Hi all,

I've a couple of jobs that run against a pool of slaves, taking whichever 
slave is free at the time. 
The problem is, if the job is already running on a slave in the pool 
Jenkins queues the next run, rather than using any of the pool's free 
slaves.

I would like Jenkins to start a new run of the job on a free slave each 
time until the pool is all in use if this is possible, so on a pool of two 
slaves I could have the job running twice at the same time, with different 
set of tests on each run instance. If I then tried to run the job for a 
third time Jenkins would queue it until a slave became free, at which point 
it would than be run.

Thnks for any help,
Jim.

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0e0c3038-74d9-4172-a93f-b1cf846055e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to