I don't know if I understood correctly, you can use the matrix
job: https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin
but it does also depend on whether other builds can use those slaves, if
that job is isolated and also those slaves then use the matrix otherwise,
you will probably need to groovy script something like:
For each slave based on some filger (Jenkins.instance.slaves.findAll{
whatever filter }.each
If it is available then run the job
Maybe someone else can suggest another way or plugin
I hope it helps
Cheers
On Friday, 30 October 2015 14:59:53 UTC+1, Jim wrote:
>
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1efe933e-e14f-47fe-b3d1-935b1ca9ca23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
