You just need to give your job a parameter of type Node. Then pass the
name of the slave on which to run (A, B or C) as a parameter when you
start the deploy job.
Eric
On 6/7/2014 4:42 AM, Levski Weng wrote:
I have several deploy server nodes in my Jenkins platform. Their deploy
procedure is similar, but they have different roles in my products line,
deploy server A is the test server of product A, and deploy server B is the
test server of product B, etc.
I write a generic deploy job which could handle deployment of all my
products, and I've written a Groovy script to invoke the scheduleBuild()
method of the job, and pass the necessary job parameters according to the
product to build, however, I don't know how to force the deploy job to run
on server A when I build product A, and run on server B when I build product
B.
Could anyone help me to achieve the goal? Thanks in advance.
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/How-to-force-a-job-to-dynamically-change-the-running-server-tp4705539.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
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].
For more options, visit https://groups.google.com/d/optout.
