[Buildbot-devel] Forcing on a given buildslave

Georges Racinet gracinet at anybox.fr
Sun Sep 9 18:03:06 UTC 2012

Le 03/09/2012 19:59, Dustin J. Mitchell a écrit :
> On Mon, Sep 3, 2012 at 1:14 PM, Jared Grubb<jared.grubb at gmail.com>  wrote:
>> I think it might be possible to swap whether the buildrequest or the slave
>> gets chosen first.
>> I've been looking at that chunk of code lately to solve another issue in
>> that area. I have 3 buildslaves, and use slave-locks to make sure only one
>> build happens per slave. The slave-assignment code doesnt check for locks
>> before randomly picking a slave ... so I'll have cases where I have two
>> slaves idle, and one or more builds assinged to the busy slave, all waiting
>> on locks.
> This code (the build request distributor) was recently rewritten.  It
> has a pretty complicated job -- coordinating the availability of slave
> builders and build requests, handling build request priorities,
> nextSlave, nextBuild, and so on.  There are a few big things lacking:
> the lock problem you describe above, and also the inability to
> prioritize builds on a particular slave across multiple builders (for
> slaves with limited concurrency).
> I'd love to see this improved!
Well, I'd love to try something, but I'm now more in need of using the 
BzrPoller in 0.8.7 branch, so I'd like to address that first.
Also, other interested people on the list seem to be more advanced on 
this than I am, and proper testing (including real-world) for all these 
conditions would take some time.

Pierre: any chance to see your code, even if not ready for proper 
integration ?


More information about the devel mailing list