Hi,
I have a build that we kick off with different parameters that I want to
utilise against all my available slaves i.e. when one is building, the next
queued build starts on another available slave.
Instead this queues on the same build that the first build kicks off on.
The build is a
Have tried using Labels applied to my slaves and the build restricted to
run on the Label but this also doesn't seem to make any difference.
This is what Slave Labels and the job option Restrict where this project
can be run are meant for. Set a specific label(s) to the slaves meant to
run the job, then restrict the job to just that label(s). Jenkins will
handle the rest. Our own Jenkins strategy relies heavily on this feature;
Is this the same job being started with two sets of different parameters?
If so check that you have Allow Concurrent builds enabled (under advanced
options I think).
If this is not enabled only one build of that job can run at one time
regardless of the times triggered.
Chris
On Tuesday,
