[Buildbot-devel] status of load balancing trees?

[Axel Hecht]

Hi,

I have managed to create some round-robin load distribution, see
http://buildbot.net/trac/ticket/36 for the patch. That distributes
build requests from a single buildset randomly on available slaves.
That should solve one of our immediate problems at Mozilla, in that it
allows us to resolve to throwing hardware at the repackaging of our
50-60 localizations per platform and app, if we want.

That still submits all buildrequest for a buildset, though. It'd be
much more reliable if the build requests would tickle in as slaves
become available, so I'm wondering how the load-balancing trees that I
read about are doing?

Background for that question is, I'm having a working set up for
building many builds per slave on a single source checkout (or so,
currently I proof-of-concept with steps.dummy.Dummy ), which currently
works via a pretty hacked Lock implementation and a scheduler that
actually locks down until a buildset is done (it blocks the timer
until then). I could envision that the solution looks differently if
the build request management was elsewhere.

Axel