On Thursday, July 26, 2012 4:43:38 PM UTC+2, mpapo - Michaël Pailloncy wrote: > > 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 ?
Because the builds will complete faster. > 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. > OK, but I obviously don't want to copy the same job configuration 10 times...
