[Buildbot-devel] SlaveLocks

Markus Kramer markus.kramer at mainconcept.de
Fri Feb 13 11:13:15 UTC 2009

Hi all,

i am just trying to setup some new buildmachines within our buildbot
system. The original idea was to have load sharing with some machines,
but somehow it does not work as expected.
I have setup multiple builders containing the following lines in their
build description:

'slavenames':[ "win-ia32-xp-b1","win-ia32-xp-b2"],
'locks': [xp_sl],

In addition i defined the lock like this in the top of config:

xp_sl = locks.SlaveLock("cpuxp2",maxCount=1)

I would have assumed that due to the fact that SlaveLocks are kept per
Slave, this would effectivly distribute the builds among these machines,
with only one build going on per Machine, but instead i still see
all the builds competing for access to machine b1.

Is the availability of locks not considered when selecting buildslave?
Is there probably some other method to make each build go to next free
slave and only queue when all of them are blocked?

Best regards,


   Markus Kramer
   Senior Engineer Codecs
   Multi-Platform Development Manager

   MainConcept GmbH
   Elisabethstr. 1
   52062 Aachen, Germany

   Phone: +49 (241) 40108-0
   Fax:     +49 (241) 40108-10
   Email:   markus.kramer at mainconcept.com
   Web:    www.mainconcept.com

   District Court Aachen: HRB 14788, Managing Directors: Muzaffer
Beygirci, David J. Richter, Eric Rodli

This message contains confidential, proprietary and/or attorney-client
privileged information or material owned by MainConcept and is intended
only for the addressed named individual(s).  The information contained
in this message may not be copied or distributed without express written
consent by an officer of MainConcept.  If the information contained in
this email is communicated under a confidentiality or non-disclosure
agreement with MainConcept, this email should be considered confidential
or proprietary written communication for the purposes of those
agreements.  Please notify the sender immediately by e-mail if you have
received this e-mail by mistake and delete this e-mail and related
information from your system.

More information about the devel mailing list