[Buildbot-devel] Full-Time buildbot developer available...!
seefeld at sympatico.ca
Tue Feb 10 19:25:23 UTC 2009
Aleksandr Milewski wrote:
> On Feb 10, 2009, at 8:54 AM, Stefan Seefeld wrote:
>> OK, it seems I expressed myself poorly. I was certainly not
>> suggesting that a build slave instance, executing one or multiple
>> builders, was cheap. My point was that I couldn't see the advantage
>> of one slave serving multiple builders / masters.
>> I fully agree that it is highly desirable to be able to restrict how
>> many builders may run in parallel.
> When considering this, keep in mind that it may be desirable for a
> slave to run builds for different masters run by different teams. I
> have a slave running a few builders for Allmydata on my amd64 box at
> home. I'd like to contribute cycles on that box to other open source
> projects as well, but I really don't want more than one or two
> builders running at once.
> In chatting with Brian about this quite a while ago, he seemed to
> think that running a single slave process that polled multiple masters
> looking for work would be the easiest way to to implement this.
> However, doing coordination in some way between multiple slaves on a
> single box would meet my requirements. Just don't assume that
> coordination between masters to achieve this is possible.
I believe you are making my point. A long time ago I proposed load
balancing to address this (http://buildbot.net/trac/ticket/42),
precisely because I found it too limiting to assume that all the
processes running on the machine were controlled by some buildbot master
that one could coordinate with. (For example, using os.getloadavg()
...ich hab' noch einen Koffer in Berlin...
More information about the devel