Why? That's simple: because no-one has implemented it yet. Jenkins is free and 
open source software. If there is feature that is missing or is important to 
you, your best bet is to implement it yourself. Just fork the code on github, 
implement the feature and send it using a pull request. 

Other option is to hire someone to do it for you. I believe Cloudbees offers 
this kind of service. Maybe others too. (I have no affiliation with Cloudbees)

Currently Jenkins seems to strongly favor the slave that already has the 
project workspace checked out. This is a very valid strategy if the project is 
large and time-consuming to check out. But clearly it does not play well if 
your projects are small and you want to execute concurrent builds. 

Currently the best you can do is to limit the number of executors on a node. 

-- Sami

Adam PAPAI <w...@wooh.hu> kirjoitti 26.7.2012 kello 18.05:

> 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 <lukas.r...@epfl.ch <mailto:lukas.r...@epfl.ch>>
>> 
>> 
>> 
>>    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: w...@wooh.hu
> Phone: +3630 3355735
> Web: http://www.wooh.hu
> 

Reply via email to