Re: Choosing the slave to run the project

I think the NodeLabel Parameter Plugin would do this. Eric On 9/6/2013 5:49 AM, Mateusz Polan'ski wrote: I want to have an upstream build, in which you choose other builds that have to be run, and the slaves on which the

RE: Choosing the slave to run the project

I want to have an upstream build, in which you choose other builds that have to be run, and the slaves on which they need to be performed. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Choosing-the-slave-to-run-the-project-tp4677458p4677463.html Sent from the Jenkins u

Re: Choosing the slave to run the project

Use the label to push builds onto a certain group labelled set of slaves On 6 Sep 2013 16:52, "Mateusz Polański" wrote: > Is there a possibility to choose the slave on which a build can be run > using > an environmental variable? > > > > -- > View this message in context: > http://jenkins-ci.3613

RE: Choosing the slave to run the project

I don't think an environment variable can be used, but in the job configuration you can specify "Restrict where this project can be run". Do you want to change the slave from run to run? If you tell the group what you are trying to achieve, you are more likely to get a useful suggestion. >

Re: Choosing the slave to run the project

When you use multi-configuration job you can select the slave by adding "Slaves" under the "Configuration Matrix section". Once you do that, you can select the slave(s) on which this job needs to be run. On Fri, Sep 6, 2013 at 2:21 PM, Mateusz Polański < mp.mateusz.polan...@gmail.com> wrote: > I