Re: Q: How to choose nodes for build based on parameter?

[jerome]

Nice! is the plugin: 
https://wiki.jenkins.io/display/JENKINS/NodeLabel+Parameter+Plugin
compatible with pipeline script (declarative or normal one)? if yes how do 
we use it into those configuration?

-- 
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/9771abad-9e1e-4fc6-8f62-4c6c2bdb8a11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: How to choose nodes for build based on parameter?

[linux.il]

Sam,
>As far as I know, this is not possible.  I would very much like this
feature as well
It's doable with the Node Label Parameter plugin - you can choose "Label"
as a parameter when creating parameterized build.

On Mon, Jul 31, 2017 at 9:34 PM, Sam K  wrote:

> As far as I know, this is not possible.  I would very much like this
> feature as well.  one example is that I can simply put a label on all the
> interested nodes and run a jenkins job that will go to each node and do a
> disk space check on them.  Is that something along what you're trying to
> do?
>
> Currently, no matter how many nodes have the label, Jenkins will go to the
> first available and run the job and exit.
>
> On Monday, July 31, 2017 at 6:28:05 AM UTC-7, Vitaly Karasik wrote:
>>
>> I have a few Jenkins slaves, some of them are labeled by "X", and others
>> with "Y" label.
>> I'd like to choose group of slaves, based on their label, when I starting
>> this job.
>> I can use "Label" as a parameter for parametrized build, but it's
>> providing  only default value, and not list of values.
>>
>> TIA,
>> Vitaly
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/VljR6r_f_9c/unsubscribe.
> To unsubscribe from this group and all its topics, 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/a64faf15-6187-4966-aef6-fffe4d333929%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/CANpTS03__1M_o2%2BBrTRMBcmQXvWODGqsoGWRLaRLxa54cmG-Pw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: How to choose nodes for build based on parameter?

[Jérôme Godbout]

If you need to target a specific node, which label match and others node
also match I don't think this is possible, jenkins master take whatever
node that match as he please (a priority number or rules would be great).

You would need a specific label on each and target that specific label.
Maybe a cron job could update the label for each node. inspect more
available disk space or something like that. have set a special label
'moreFreeSpace' or something like that. Note sure you can change label at
runtime into Jenkins, but I never tried. I just throwing idea here.


[image: bodycad] 
Jerome Godbout
Software Developer
2035 rue du Haut-Bord, Québec, QC, Canada. G1N 4R7
T:  +1 418 527-1388
E: jer...@bodycad.com
www.bodycad.com

The contents of this email message and any attachments are intended solely
for the addressee(s) and may contain confidential and/or privileged
information and may be legally protected from disclosure. If you are not
the intended recipient of this message or their agent, or if this message
has been addressed to you in error, please immediately alert the sender by
reply email and then delete this message and any attachments. If you are
not the intended recipient, you are hereby notified that any use,
dissemination, copying, or storage of this message or its attachments is
strictly prohibited.

Le contenu de ce message et les pièces jointes sont destinés uniquement
pour le(s) destinataire(s) et peuvent contenir des informations
confidentielles et / ou privilégiées qui peuvent être protégées légalement
contre toute divulgation. Si vous n'êtes pas le destinataire de ce message
ou son agent, ou si ce message vous a été adressé par erreur, s’il vous
plaît avertir immédiatement l'expéditeur par courriel de réponse, puis
supprimer ce message et les pièces jointes. Si vous n'êtes pas le
destinataire prévu, vous êtes par la présente informé que toute
utilisation, diffusion, copie, ou stockage de ce message ou de ses pièces
jointes est strictement interdit.

On Mon, Jul 31, 2017 at 2:34 PM, Sam K  wrote:

> As far as I know, this is not possible.  I would very much like this
> feature as well.  one example is that I can simply put a label on all the
> interested nodes and run a jenkins job that will go to each node and do a
> disk space check on them.  Is that something along what you're trying to
> do?
>
> Currently, no matter how many nodes have the label, Jenkins will go to the
> first available and run the job and exit.
>
> On Monday, July 31, 2017 at 6:28:05 AM UTC-7, Vitaly Karasik wrote:
>>
>> I have a few Jenkins slaves, some of them are labeled by "X", and others
>> with "Y" label.
>> I'd like to choose group of slaves, based on their label, when I starting
>> this job.
>> I can use "Label" as a parameter for parametrized build, but it's
>> providing  only default value, and not list of values.
>>
>> TIA,
>> Vitaly
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/VljR6r_f_9c/unsubscribe.
> To unsubscribe from this group and all its topics, 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/a64faf15-6187-4966-aef6-fffe4d333929%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/CAKmu%2Be1%3D9Aik_%3Dq8yZyBE%3D7ksngue8%3D8ZR6tfCx2uDszKmBgfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: How to choose nodes for build based on parameter?

[Sam K]

As far as I know, this is not possible.  I would very much like this 
feature as well.  one example is that I can simply put a label on all the 
interested nodes and run a jenkins job that will go to each node and do a 
disk space check on them.  Is that something along what you're trying to 
do?  

Currently, no matter how many nodes have the label, Jenkins will go to the 
first available and run the job and exit.  

On Monday, July 31, 2017 at 6:28:05 AM UTC-7, Vitaly Karasik wrote:
>
> I have a few Jenkins slaves, some of them are labeled by "X", and others 
> with "Y" label.
> I'd like to choose group of slaves, based on their label, when I starting 
> this job. 
> I can use "Label" as a parameter for parametrized build, but it's 
> providing  only default value, and not list of values.
>
> TIA,
> Vitaly
>

-- 
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/a64faf15-6187-4966-aef6-fffe4d333929%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: How to choose nodes for build based on parameter?

[jerome]

Check for choice parameters plugins like:
https://wiki.jenkins.io/display/JENKINS/Extensible+Choice+Parameter+plugin
there also a validation plugins if you allow custom entry.

I guess the node selection should work (take care " and not '):

node("${NODE_LABEL}")




-- 
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/14549f00-f27b-440b-b73b-e7c031874a01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: How to choose nodes for build based on parameter?

[linux.il]

Mark, thank you!
As far as I remember, I already have this plugin and played with its
options. It does allow choose some nodes, but I prefer to choose by label.
I.e., if I choose  "X" label, job will executed on all slaves which have
this label.


On Mon, Jul 31, 2017 at 6:06 PM, Mark Waite 
wrote:

> Have you checked the node label parameter plugin?  It seems like it
> matches what you need.
>
> If you need the matrix  job to run on all agents which match a label, then
> you want the elastic axis plugin.
>
> Pipeline can handle that case as well.
>
> Mark Waite
>
> On Mon, Jul 31, 2017, 7:28 AM Vitaly Karasik  wrote:
>
>> I have a few Jenkins slaves, some of them are labeled by "X", and others
>> with "Y" label.
>> I'd like to choose group of slaves, based on their label, when I starting
>> this job.
>> I can use "Label" as a parameter for parametrized build, but it's
>> providing  only default value, and not list of values.
>>
>> TIA,
>> Vitaly
>>
>> --
>> 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/0c82441b-97e6-4404-a888-
>> efa0d3d57973%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/VljR6r_f_9c/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAO49JtETHCuJZVez%3D1%2BB6jqq1L1KpRp578Z7E8Ngh7xupU3
> JGA%40mail.gmail.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/CANpTS02FxBdC8GDdQm%2BYoGw29rJAJZnO8%3DdXcSWxxzBxwS1Tvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: How to choose nodes for build based on parameter?

[Mark Waite]

Have you checked the node label parameter plugin?  It seems like it matches
what you need.

If you need the matrix  job to run on all agents which match a label, then
you want the elastic axis plugin.

Pipeline can handle that case as well.

Mark Waite

On Mon, Jul 31, 2017, 7:28 AM Vitaly Karasik  wrote:

> I have a few Jenkins slaves, some of them are labeled by "X", and others
> with "Y" label.
> I'd like to choose group of slaves, based on their label, when I starting
> this job.
> I can use "Label" as a parameter for parametrized build, but it's
> providing  only default value, and not list of values.
>
> TIA,
> Vitaly
>
> --
> 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/0c82441b-97e6-4404-a888-efa0d3d57973%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/CAO49JtETHCuJZVez%3D1%2BB6jqq1L1KpRp578Z7E8Ngh7xupU3JGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Q: How to choose nodes for build based on parameter?

[Vitaly Karasik]

I have a few Jenkins slaves, some of them are labeled by "X", and others 
with "Y" label.
I'd like to choose group of slaves, based on their label, when I starting 
this job. 
I can use "Label" as a parameter for parametrized build, but it's providing 
 only default value, and not list of values.

TIA,
Vitaly

-- 
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/0c82441b-97e6-4404-a888-efa0d3d57973%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.