Have a look at this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin
In its global config you can specify a list of categories. So if you specify Server1, Server2, Server3 Then in your jobs you can throttle based on category, and select which category the job belongs to. You can then limit each category to one job per node. Job1a - select Server1 category Job1b - select Server1 category Job2a - select Server2 category Job1a and Job1b will run on different nodes, or wait if required. Job2a can run at the same time on same node as job1a or job1b as its different category. Writing this on my phone but I can try give more detail tomorrow when I am at work if needed. Hope this helps, Geoff On 15 Apr 2013, at 16:00, Aswini Rajasekaran <aswini.rajaseka...@gmail.com> wrote: Hi, I am running 20 different test suites using jboss and selenium. Each test has been configured to use which port and which server instance of jboss. I have 4 slaves each with 2 executors and master with 3 executors. Is it possible to dynamically allocate the itest jobs to the slaves, provided the jobs which uses server1 instance shouldn't run on the same slave/master. Jenkins should dynamically assign the jobs to different slave nodes if the job runs the same instance of jboss. How is this done? Thanks, Aswini -- 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. -- 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.
