Mixing
How do I make Jenkins pipeline run in (any) agent machine, but never master?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
My Jenkins pipeline randomly alternates between running on master and on agent (slave) machines.
The whole pipeline uses has only one agent statement, thus:
pipeline {
agent any
How can I get the build to run in load-balanced agents, and never master?
Maybe it could be done with
agent { label 'some-label' }. Is there a predefined label that specifies agents and not master? Or do I have to label all agents myself?This and this show how to choose a specific agent, but I want random balancing between agent machines.
This question discussesagent anyvsagent none, but neither of those blocks the master from being used.
This page recommends wrapping everything in anodestanza, but that seems to force the build to run on master or a specified node, which again does not allow balancing of agents.
jenkins jenkins-pipeline
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
add a comment |
My Jenkins pipeline randomly alternates between running on master and on agent (slave) machines.
The whole pipeline uses has only one agent statement, thus:
pipeline {
agent any
How can I get the build to run in load-balanced agents, and never master?
Maybe it could be done with
agent { label 'some-label' }. Is there a predefined label that specifies agents and not master? Or do I have to label all agents myself?This and this show how to choose a specific agent, but I want random balancing between agent machines.
This question discussesagent anyvsagent none, but neither of those blocks the master from being used.
This page recommends wrapping everything in anodestanza, but that seems to force the build to run on master or a specified node, which again does not allow balancing of agents.
jenkins jenkins-pipeline
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
You can add labels to workers and use that in nodenode("label") { //execution statement }here instead of label you can give node name to run in specific node. there is label section in configure node page. labels are separated by white-space
– jos
Jan 3 at 12:43
add a comment |
My Jenkins pipeline randomly alternates between running on master and on agent (slave) machines.
The whole pipeline uses has only one agent statement, thus:
pipeline {
agent any
How can I get the build to run in load-balanced agents, and never master?
Maybe it could be done with
agent { label 'some-label' }. Is there a predefined label that specifies agents and not master? Or do I have to label all agents myself?This and this show how to choose a specific agent, but I want random balancing between agent machines.
This question discussesagent anyvsagent none, but neither of those blocks the master from being used.
This page recommends wrapping everything in anodestanza, but that seems to force the build to run on master or a specified node, which again does not allow balancing of agents.
jenkins jenkins-pipeline
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
My Jenkins pipeline randomly alternates between running on master and on agent (slave) machines.
The whole pipeline uses has only one agent statement, thus:
pipeline {
agent any
How can I get the build to run in load-balanced agents, and never master?
Maybe it could be done with
agent { label 'some-label' }. Is there a predefined label that specifies agents and not master? Or do I have to label all agents myself?This and this show how to choose a specific agent, but I want random balancing between agent machines.
This question discussesagent anyvsagent none, but neither of those blocks the master from being used.
This page recommends wrapping everything in anodestanza, but that seems to force the build to run on master or a specified node, which again does not allow balancing of agents.
jenkins jenkins-pipeline
jenkins jenkins-pipeline
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
edited Jan 3 at 11:03
Joshua Fox
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
asked Jan 3 at 10:46
Joshua FoxJoshua Fox
8,281115180
8,281115180
You can add labels to workers and use that in nodenode("label") { //execution statement }here instead of label you can give node name to run in specific node. there is label section in configure node page. labels are separated by white-space
– jos
Jan 3 at 12:43
add a comment |
You can add labels to workers and use that in nodenode("label") { //execution statement }here instead of label you can give node name to run in specific node. there is label section in configure node page. labels are separated by white-space
– jos
Jan 3 at 12:43
You can add labels to workers and use that in node
node("label") { //execution statement } here instead of label you can give node name to run in specific node. there is label section in configure node page. labels are separated by white-space– jos
Jan 3 at 12:43
You can add labels to workers and use that in node
node("label") { //execution statement } here instead of label you can give node name to run in specific node. there is label section in configure node page. labels are separated by white-space– jos
Jan 3 at 12:43
add a comment |
2 Answers
2
active
oldest
votes
You can use node('!master') {...} or agent { label '!master' } syntax. See more details there.
Also there is a solution from Jenkins Best Practices page for setting limitation on master node itself:
If you have a more complex security setup that allows some users to only configure jobs, but not administer Jenkins, you need to prevent them from running builds on the master node, otherwise they have unrestricted access into the JENKINS_HOME directory. You can do this by setting the executor count to zero. Instead, make sure all jobs run on agents. This ensures that the jenkins master can scale to support many more jobs, and it also protects builds from modifying potentially sensitive data on $JENKINS_HOME accidentally/maliciously. If you need some jobs to run on the master (e.g. backups of Jenkins itself), use the Job Restrictions Plugin to limit which jobs can be executed there.
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
add a comment |
When configuring node restrictions based on labels for freestyle jobs in the jenkins web interface, you can do this with the expression !master. The boolean operators || and && are also supported.
I'm not sure whether the pipeline configuration supports the same expression syntax, but it's worth a shot.
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54020776%2fhow-do-i-make-jenkins-pipeline-run-in-any-agent-machine-but-never-master%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can use node('!master') {...} or agent { label '!master' } syntax. See more details there.
Also there is a solution from Jenkins Best Practices page for setting limitation on master node itself:
If you have a more complex security setup that allows some users to only configure jobs, but not administer Jenkins, you need to prevent them from running builds on the master node, otherwise they have unrestricted access into the JENKINS_HOME directory. You can do this by setting the executor count to zero. Instead, make sure all jobs run on agents. This ensures that the jenkins master can scale to support many more jobs, and it also protects builds from modifying potentially sensitive data on $JENKINS_HOME accidentally/maliciously. If you need some jobs to run on the master (e.g. backups of Jenkins itself), use the Job Restrictions Plugin to limit which jobs can be executed there.
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
add a comment |
You can use node('!master') {...} or agent { label '!master' } syntax. See more details there.
Also there is a solution from Jenkins Best Practices page for setting limitation on master node itself:
If you have a more complex security setup that allows some users to only configure jobs, but not administer Jenkins, you need to prevent them from running builds on the master node, otherwise they have unrestricted access into the JENKINS_HOME directory. You can do this by setting the executor count to zero. Instead, make sure all jobs run on agents. This ensures that the jenkins master can scale to support many more jobs, and it also protects builds from modifying potentially sensitive data on $JENKINS_HOME accidentally/maliciously. If you need some jobs to run on the master (e.g. backups of Jenkins itself), use the Job Restrictions Plugin to limit which jobs can be executed there.
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
add a comment |
You can use node('!master') {...} or agent { label '!master' } syntax. See more details there.
Also there is a solution from Jenkins Best Practices page for setting limitation on master node itself:
If you have a more complex security setup that allows some users to only configure jobs, but not administer Jenkins, you need to prevent them from running builds on the master node, otherwise they have unrestricted access into the JENKINS_HOME directory. You can do this by setting the executor count to zero. Instead, make sure all jobs run on agents. This ensures that the jenkins master can scale to support many more jobs, and it also protects builds from modifying potentially sensitive data on $JENKINS_HOME accidentally/maliciously. If you need some jobs to run on the master (e.g. backups of Jenkins itself), use the Job Restrictions Plugin to limit which jobs can be executed there.
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
You can use node('!master') {...} or agent { label '!master' } syntax. See more details there.
Also there is a solution from Jenkins Best Practices page for setting limitation on master node itself:
If you have a more complex security setup that allows some users to only configure jobs, but not administer Jenkins, you need to prevent them from running builds on the master node, otherwise they have unrestricted access into the JENKINS_HOME directory. You can do this by setting the executor count to zero. Instead, make sure all jobs run on agents. This ensures that the jenkins master can scale to support many more jobs, and it also protects builds from modifying potentially sensitive data on $JENKINS_HOME accidentally/maliciously. If you need some jobs to run on the master (e.g. backups of Jenkins itself), use the Job Restrictions Plugin to limit which jobs can be executed there.
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
edited Jan 3 at 14:02
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
answered Jan 3 at 12:19
biruk1230biruk1230
1,1441417
1,1441417
add a comment |
add a comment |
When configuring node restrictions based on labels for freestyle jobs in the jenkins web interface, you can do this with the expression !master. The boolean operators || and && are also supported.
I'm not sure whether the pipeline configuration supports the same expression syntax, but it's worth a shot.
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
add a comment |
When configuring node restrictions based on labels for freestyle jobs in the jenkins web interface, you can do this with the expression !master. The boolean operators || and && are also supported.
I'm not sure whether the pipeline configuration supports the same expression syntax, but it's worth a shot.
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
add a comment |
When configuring node restrictions based on labels for freestyle jobs in the jenkins web interface, you can do this with the expression !master. The boolean operators || and && are also supported.
I'm not sure whether the pipeline configuration supports the same expression syntax, but it's worth a shot.
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
When configuring node restrictions based on labels for freestyle jobs in the jenkins web interface, you can do this with the expression !master. The boolean operators || and && are also supported.
I'm not sure whether the pipeline configuration supports the same expression syntax, but it's worth a shot.
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
answered Jan 3 at 12:48
Wim CoenenWim Coenen
57.4k8136223
57.4k8136223
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54020776%2fhow-do-i-make-jenkins-pipeline-run-in-any-agent-machine-but-never-master%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You can add labels to workers and use that in node
node("label") { //execution statement }here instead of label you can give node name to run in specific node. there is label section in configure node page. labels are separated by white-space– jos
Jan 3 at 12:43