[Buildbot-devel] Dynamic Registration of Slaves

[P. Christeas]

On Saturday 25 September 2010, Phil Parsonage wrote:
>   Hi,
> 
> I'm looking at using buildbot to perform both build and test tasks. As
> far as I can tell from the docs, I have to register all my build slaves
> in a master.cfg file. What I would like to achieve is to allow dynamic
> registration of slaves, so that machines register themselves to a build
> master with information of what they are capable of (probably using OS,
> OS version, and version of developer tools) dynamically, when they
> become available. ...

I think your case is already covered by the present design:
the master.cfg will list /all the possible slaves/, i.e. all the people who 
have offered to let their machines become build slaves. But they don't need to 
be online all the time.

Think of the buildslaves at master.cfg as sth. like a passwd file. Not all 
users are always logged in .

Depending on the slaves that are currently online, the build master will chose 
one among them that matches the scheduler request (that's where OS and env 
matching would take place). The algorithm is such, that the build master will 
/first/ wait for a build slave to be available, and then decide if the build 
can actually be started. So, yes, it will pick an available slave, hopefully, 
the way you asked for.


-- 
Say NO to spam and viruses. Stop using Microsoft Windows!