Ok, sorry ! I had not seen your screenshot. Jenkins behaviour does not surprise me. It seems to set the priority to slave where a build has already be done. Otherwise, why do you need this feature ? I'm sure that if you create 10 jobs and launch 10 builds on each, Jenkins will use all available slots without restrict builds to the prefered slave.
2012/7/26 Lukas Rytz <lukas.r...@epfl.ch> > There was a delay of ~10 seconds between starting each build. > > You can see some details in the screenshot of my original > post<https://groups.google.com/d/msg/jenkinsci-users/wFdylTzyczM/4Xrfs0Tjj2UJ>: > We have 5 slaves here, > one of them was already running one job, all of the others were idle. > > It would be nice if the scheduling was configurable. It seems that the > "Throttle Concurrent > Builds" plugin [1] works in that direction: it can make sure to never run > more than X builds > on one machine. What I'm looking for is not a limited, but a balanced > scheduling. > > Lukas > > > [1] > https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin > > > > > On Thursday, July 26, 2012 3:56:56 PM UTC+2, mpapo - Michaël Pailloncy > wrote: >> >> Did you launch your 6 differents jobs at the same time ? >> It's curious that Jenkins use the same slave for 5/6 builds. >> How many slaves do you have ? >> >>
