RE: Teaching an old job new tricks

2016-08-17 Thread Ginga, Dick 
Thank you Mark

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Wednesday, August 17, 2016 10:03 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Teaching an old job new tricks

Labels do not have any concept of affinity as far as I know.

On Wed, Aug 17, 2016 at 7:40 AM Ginga, Dick 
<dick.gi...@perkinelmer.com<mailto:dick.gi...@perkinelmer.com>> wrote:
Does the use of node label contain a notion of “affinity”. In other words, I 
would like a build to go to node A always, unless node A is unavailable.

I implemented my own failover by using a node label parameter with a default 
node of A and a “possible nodes” of the failover node.

From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> 
[mailto:jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>]
 On Behalf Of Mark Waite
Sent: Tuesday, August 16, 2016 7:15 PM
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: Teaching an old job new tricks


On Tue, Aug 16, 2016 at 3:44 PM Bruce Epstein 
<goo...@zeusprod.com<mailto:goo...@zeusprod.com>> 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) 
<ingu...@cisco.com<mailto:ingu...@cisco.com>> wrote:
Use the Configuration Slicing Plugin : 
https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.jenkins-2Dci.org_display_JENKINS_Configuration-2BSlicing-2BPlugin=DQMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=nXhfG9PkqmRpZIuD5R5-RGLY9x3zWMXVPKMj_OmzvYA=Vj87PArNuHgsZ6OdHj0v-G0TyK9NSwesFgJg3yOp4us=>
 to mass assign a label to jobs that are not tied to any node all at once.

-Indra

From: <jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>> on 
behalf of Bruce Epstein <goo...@zeusprod.com<mailto:goo...@zeusprod.com>>
Reply-To: "jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>" 
<jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>>

Date: Tuesday, August 16, 2016 at 1:16 PM
To: Jenkins Users 
<jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>>

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://urldefense.proofpoint.com/v2/url?u=https-3A__webmail.novantas.com_owa_redir.aspx-3FSURL-3DbccvBaZmiAUZEiOjb7fb5V0hm90n-5FX4zGXw8tWkw-2D8ka1WNgEcbTCGgAdAB0AHAAcwA6AC8ALwB3AGkAawBpAC4AagBlAG4AawBpAG4AcwAtAGMAaQAuAG8AcgBnAC8AZABpAHMAcABsAGEAeQAvAEoARQBOAEsASQBOAFMALwBOAG8AZABlAEwAYQBiAGUAbAArAFAAYQByAGEAbQBlAHQAZQByACsAUABsAHUAZwBpAG4A-26URL-3Dhttps-253a-252f-252fwiki.jenkins-2Dci.org-252fdisplay-252fJENKINS-252fNodeLabel-252bParameter-252bPlugin=DQMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=nXhfG9PkqmRpZIuD5R5-RGLY9x3zWMXVPKMj_OmzvYA=th0wJemjUB73CcgPWJ

Re: Teaching an old job new tricks

2016-08-17 Thread Mark Waite 
Labels do not have any concept of affinity as far as I know.

On Wed, Aug 17, 2016 at 7:40 AM Ginga, Dick <dick.gi...@perkinelmer.com>
wrote:

> Does the use of node label contain a notion of “affinity”. In other words,
> I would like a build to go to node A always, unless node A is unavailable.
>
>
>
> I implemented my own failover by using a node label parameter with a
> default node of A and a “possible nodes” of the failover node.
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Mark Waite
> *Sent:* Tuesday, August 16, 2016 7:15 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Teaching an old job new tricks
>
>
>
>
>
> On Tue, Aug 16, 2016 at 3:44 PM Bruce Epstein <goo...@zeusprod.com> 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) <
> ingu...@cisco.com> wrote:
>
> Use the Configuration Slicing Plugin :
> https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.jenkins-2Dci.org_display_JENKINS_Configuration-2BSlicing-2BPlugin=DQMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=nXhfG9PkqmRpZIuD5R5-RGLY9x3zWMXVPKMj_OmzvYA=Vj87PArNuHgsZ6OdHj0v-G0TyK9NSwesFgJg3yOp4us=>
>  to
> mass assign a label to jobs that are not tied to any node all at once.
>
>
>
> -Indra
>
>
>
> *From: *<jenkins...@googlegroups.com> on behalf of Bruce Epstein <
> goo...@zeusprod.com>
> *Reply-To: *"jenkins...@googlegroups.com" <jenkins...@googlegroups.com>
>
>
> *Date: *Tuesday, August 16, 2016 at 1:16 PM
>
> *To: *Jenkins Users <jenkins...@googlegroups.com>
>
>
> *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://urldefense.proofpoint.com/v2/url?u=https-3A__webmail.novantas.com_owa_redir.aspx-3FSURL-3DbccvBaZmiAUZEiOjb7fb5V0hm90n-5FX4zGXw8tWkw-2D8ka1WNgEcbTCGgAdAB0AHAAcwA6AC8ALwB3AGkAawBpAC4AagBlAG4AawBpAG4AcwAtAGMAaQAuAG8AcgBnAC8AZABpAHMAcABsAGEAeQAvAEoARQBOAEsASQBOAFMALwBOAG8AZABlAEwAYQBiAGUAbAArAFAAYQByAGEAbQBlAHQAZQByACsAUABsAHUAZwBpAG4A-26URL-3Dhttps-253a-252f-252fwiki.jenkins-2Dci.org-252fdisplay-252fJENKINS-252fNodeLabel-252bParameter-252bPlugin=DQMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=nXhfG9PkqmRpZIuD5R5-RGLY9x3zWMXVPKMj_OmzvYA=th0wJemjUB73CcgPWJcL-leHSh66pbDjRn2BcpDR35s=>
>
> Will that work with old jobs, causing them to run on one of the new agent
> nodes instead of the maste

RE: Teaching an old job new tricks

2016-08-17 Thread Ginga, Dick 
Does the use of node label contain a notion of “affinity”. In other words, I 
would like a build to go to node A always, unless node A is unavailable.

I implemented my own failover by using a node label parameter with a default 
node of A and a “possible nodes” of the failover node.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: Tuesday, August 16, 2016 7:15 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Teaching an old job new tricks


On Tue, Aug 16, 2016 at 3:44 PM Bruce Epstein 
<goo...@zeusprod.com<mailto:goo...@zeusprod.com>> 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) 
<ingu...@cisco.com<mailto:ingu...@cisco.com>> wrote:
Use the Configuration Slicing Plugin : 
https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.jenkins-2Dci.org_display_JENKINS_Configuration-2BSlicing-2BPlugin=DQMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=nXhfG9PkqmRpZIuD5R5-RGLY9x3zWMXVPKMj_OmzvYA=Vj87PArNuHgsZ6OdHj0v-G0TyK9NSwesFgJg3yOp4us=>
 to mass assign a label to jobs that are not tied to any node all at once.

-Indra

From: <jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>> on 
behalf of Bruce Epstein <goo...@zeusprod.com<mailto:goo...@zeusprod.com>>
Reply-To: "jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>" 
<jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>>

Date: Tuesday, August 16, 2016 at 1:16 PM
To: Jenkins Users 
<jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>>

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://urldefense.proofpoint.com/v2/url?u=https-3A__webmail.novantas.com_owa_redir.aspx-3FSURL-3DbccvBaZmiAUZEiOjb7fb5V0hm90n-5FX4zGXw8tWkw-2D8ka1WNgEcbTCGgAdAB0AHAAcwA6AC8ALwB3AGkAawBpAC4AagBlAG4AawBpAG4AcwAtAGMAaQAuAG8AcgBnAC8AZABpAHMAcABsAGEAeQAvAEoARQBOAEsASQBOAFMALwBOAG8AZABlAEwAYQBiAGUAbAArAFAAYQByAGEAbQBlAHQAZQByACsAUABsAHUAZwBpAG4A-26URL-3Dhttps-253a-252f-252fwiki.jenkins-2Dci.org-252fdisplay-252fJENKINS-252fNodeLabel-252bParameter-252bPlugin=DQMFaQ=3mGIBQKb1eS1YDHb7ax3kFkT2UAGBJ12p2lcECIjhXk=SXz9subj7EUWDFIuiAjJSXBLM9pAzGIduhHWvfq5re0=nXhfG9PkqmRpZIuD5R5-RGLY9x3zWMXVPKMj_OmzvYA=th0wJemjUB73CcgPWJcL-leHSh66pbDjRn2BcpDR35s=>

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 jenkinsci-use...@googlegroups.com<mailto:jenkinsci-use...@googlegroups.com>.

To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8a

Re: Teaching an old job new tricks

2016-08-16 Thread Mark Waite 
On Tue, Aug 16, 2016 at 3:44 PM Bruce Epstein  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) <
>> ingu...@cisco.com> 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:  on behalf of Bruce Epstein <
>>> goo...@zeusprod.com>
>>> Reply-To: "jenkins...@googlegroups.com" 
>>>
>>
>>> Date: Tuesday, August 16, 2016 at 1:16 PM
>>>
>> To: Jenkins Users 
>>>
>>
>>> 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
>>> 
>>>
>>> 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 jenkinsci-use...@googlegroups.com.
>>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com
>>> 
>>> .
>>> 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 jenkinsci-use...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/D3D8C322.5AE4A%25ingunawa%40cisco.com
>>> 
>>> .
>>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e70472f5-6012-4d5b-9eab-a3790d9c5ef3%40googlegroups.com
>

Re: Teaching an old job new tricks

2016-08-16 Thread Bruce Epstein 
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?

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) <
> ingu...@cisco.com > 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:  on behalf of Bruce 
>> Epstein 
>> Reply-To: "jenkins...@googlegroups.com " <
>> jenkins...@googlegroups.com >
>> Date: Tuesday, August 16, 2016 at 1:16 PM
>> To: Jenkins Users 
>> 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 
>> 
>>
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com
>>  
>> 
>> .
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/D3D8C322.5AE4A%25ingunawa%40cisco.com
>>  
>> 
>> .
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e70472f5-6012-4d5b-9eab-a3790d9c5ef3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Teaching an old job new tricks

2016-08-16 Thread Bruce Epstein 
Thanks. I will look into it.

But, it seems like the "Label" is only a property of newly created jobs, 
not existing ones.

Am I misunderstanding something?

On Tuesday, August 16, 2016 at 4:19:30 PM UTC-4, Indra Gunawan (ingunawa) 
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:  on behalf of Bruce 
> Epstein 
> Reply-To: "jenkins...@googlegroups.com " <
> jenkins...@googlegroups.com >
> Date: Tuesday, August 16, 2016 at 1:16 PM
> To: Jenkins Users 
> 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 
> 
>
> 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 jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com
>  
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/076e079a-1902-4526-9285-d414a0f56985%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Teaching an old job new tricks

2016-08-16 Thread Mark Waite 
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) 
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:  on behalf of Bruce Epstein <
> goo...@zeusprod.com>
> Reply-To: "jenkinsci-users@googlegroups.com" <
> jenkinsci-users@googlegroups.com>
> Date: Tuesday, August 16, 2016 at 1:16 PM
> To: Jenkins Users 
> 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
> 
>
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/D3D8C322.5AE4A%25ingunawa%40cisco.com
> 
> .
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGGu9mzSiUGbX-pQp%2Bs%3DkhZgZkWsmgKEXuommyEOBb0UA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Teaching an old job new tricks

2016-08-16 Thread Indra Gunawan (ingunawa) 
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: 
> on 
behalf of Bruce Epstein >
Reply-To: 
"jenkinsci-users@googlegroups.com" 
>
Date: Tuesday, August 16, 2016 at 1:16 PM
To: Jenkins Users 
>
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

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 
jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8a88c69f-bf54-4bd8-8009-e73c2f42895b%40googlegroups.com.
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D3D8C322.5AE4A%25ingunawa%40cisco.com.
For more options, visit https://groups.google.com/d/optout.