On Tue, Aug 16, 2016 at 3:44 PM Bruce Epstein <[email protected]> wrote:
> Thanks, I will try that. > > I guess this gets to the heart of my question... > > If I make it so that an old job won't run on builder, will it fail over to > the newly created node? > > Yes, it will switch freely from one node to another unless you have tied the job to a specific node. That's one of the reasons to tie a job to a capability based label rather than tying it to a specific node name. Mark Waite > That is, will old jobs run on the new node, if cajoled properly, or will > they just fail altogether? > > > On Tuesday, August 16, 2016 at 4:23:38 PM UTC-4, Mark Waite wrote: > >> You might also consider changing the setting of the master node. >> >> The "Usage" field of the master node configuration should have a pick >> list with two choices, either "Use this node as much as possible" (the >> default), or "Only build jobs with label expressions matching this node". >> That will tend to keep most jobs off your master node (at least it does for >> me). >> >> Mark Waite >> >> On Tue, Aug 16, 2016 at 2:19 PM Indra Gunawan (ingunawa) < >> [email protected]> wrote: >> > Use the Configuration Slicing Plugin : >>> https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin to >>> mass assign a label to jobs that are not tied to any node all at once. >>> >>> -Indra >>> >>> From: <[email protected]> on behalf of Bruce Epstein < >>> [email protected]> >>> Reply-To: "[email protected]" <[email protected]> >>> >> >>> Date: Tuesday, August 16, 2016 at 1:16 PM >>> >> To: Jenkins Users <[email protected]> >>> >> >>> Subject: Teaching an old job new tricks >>> >> Hi All, >>> >>> Thanks to those who answered my previous question about setting up >>> agents. >>> >>> I now have two new agent nodes set up and want to move old jobs off the >>> master, so the master won't be used for any building (just admin). >>> >>> How do I prevent jobs from running on the master? Do I just set "number >>> of executors" to zero? >>> >>> For new jobs, I see the choice in their configuration allowing me to >>> decide where to run the job, so I can force it to run on the agent node not >>> the master. >>> >>> I understand old jobs are supposed to run on the master, but I don't >>> want them to any more. Even cloned (new) jobs seem to not have the >>> "Restrict where this job runs" configuration option, so I assume they will >>> run on the master (as did the job from which they were cloned.) >>> >>> What are my options? >>> >>> This plugin seems to be one possibility for setting the node at build >>> time (I imagine I can set its default to specify a new node for building?) >>> >>> https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin >>> <https://webmail.novantas.com/owa/redir.aspx?SURL=bccvBaZmiAUZEiOjb7fb5V0hm90n_X4zGXw8tWkw-8ka1WNgEcbTCGgAdAB0AHAAcwA6AC8ALwB3AGkAawBpAC4AagBlAG4AawBpAG4AcwAtAGMAaQAuAG8AcgBnAC8AZABpAHMAcABsAGEAeQAvAEoARQBOAEsASQBOAFMALwBOAG8AZABlAEwAYQBiAGUAbAArAFAAYQByAGEAbQBlAHQAZQByACsAUABsAHUAZwBpAG4A&URL=https%3a%2f%2fwiki.jenkins-ci.org%2fdisplay%2fJENKINS%2fNodeLabel%2bParameter%2bPlugin> >>> >>> Will that work with old jobs, causing them to run on one of the new >>> agent nodes instead of the master? >>> >>> Inquiring minds want to know! >>> >>> Thanks again in advance. >>> >>> Cheers >>> Bruce >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/D3D8C322.5AE4A%25ingunawa%40cisco.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/D3D8C322.5AE4A%25ingunawa%40cisco.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/e70472f5-6012-4d5b-9eab-a3790d9c5ef3%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/e70472f5-6012-4d5b-9eab-a3790d9c5ef3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEHQWdaN2up2ka6WLVyGHaMFPuV8TJj5jVMCMfY1unpsw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
