[Buildbot-devel] Followup: Triggerable with waitforFinish=True requires build slot

Bob Hood bhood2 at comcast.net
Tue Dec 17 20:45:39 UTC 2013


On 12/13/2013 6:53 AM, Charles Lepple wrote:
> On Dec 13, 2013, at 8:30 AM, Bob Hood wrote:
>> Any suggestions regarding how I could configure to keep the build slots
>> confined to a collection of builds?  Or I would also entertain doing some
>> "hacking" of the Buildbot Master code to see what I can do there (perhaps
>> temporarily hand off the sole build slot to another lane) if somebody would
>> point me at the salient module(s) and lines of code.
> If I am not mistaken, using a lock on the main build lane (Builder) with waitForFinish=True (and removing max_builds=N) should prevent a second main build from starting before all of the other toolkits finish.
>
>    http://docs.buildbot.net/current/manual/cfg-interlocks.html#interlocks
>
>    http://docs.buildbot.net/current/manual/cfg-builders.html
>
> You can think of max_builds as being a crude counting lock per slave (and it sounds like you have a 1:1 Builder to Buildslave ratio).


Using an "exclusive" lock in the main build lanes solved the issue elegantly. 
Thanks again for pointing me at this, Charles.  :)




More information about the devel mailing list