Anyway: Why don't we have a "round-robin" load balance option?
I hate that sometimes jenkins uses 3 full node and the other 10 is unused... How hard is to implement it? Michaël Pailloncy wrote:
Ok, I'm not sure that 6 builds of the same job (for example) will be faster if you run them on 6 slaves or in one slave with 6 slots. Taking in account that the 6 slaves have the same capacity and are properly sized to accommodate 6 simultaneous builds. Maybe it could be in interesting experience to lead :) 2012/7/26 Lukas Rytz <[email protected] <mailto:[email protected]>> 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...
-- Adam PAPAI E-mail: [email protected] Phone: +3630 3355735 Web: http://www.wooh.hu
