Well... because it would be much easier to change the value for my main slave in just one place, rather than have to go from job to job and change the label expression for "restrict where this project can be run".
To make it clear: - I have severall nodes - a lot of jobs - some of them must run on the node that at that moment is the main slave - at each moment there is just one main slave - main slave changes often (and that does not means that the previous main slave is now offline) So, it would be really nice if I can configure my jobs that should run at main slave, by saying that they have to run on the node that maches the value of my global property MAIN_SLAVE. Terça-feira, 24 de Setembro de 2013 15:46:20 UTC+1, LesMikesell escreveu: > > On Tue, Sep 24, 2013 at 9:40 AM, Tânia Magalhães > <taniama...@gmail.com <javascript:>> wrote: > > Hi! > > > > Under "Restrict where this project can be run", it is possible at label > > expression add a global property key (name) ? > > > > I have a global property named MAIN_SLAVE which value sometimes changes. > And > > I have some jobs that I want to run in that main slave. > > I already tried to add %MAIN_SLAVE% to label expression, but it reports > that > > there is no label or node with that name... > > Any ideas on how to do it? > > Why don't you just apply the label you want to the nodes you want and > leave it that way? You can give nodes more than one label if you are > doing something more complicated. > > -- > Les Mikesell > lesmi...@gmail.com <javascript:> > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
