[Buildbot-devel] Multiple change sources and scheduler issues

[Dustin J. Mitchell]

On Tue, Jul 1, 2008 at 8:34 AM, Duncan Ferguson
<duncan.ferguson at altinity.com> wrote:
> I have set up my buildbot v0.77 with a number of change sources and
> Schedulers.  The problem I have is that when a change is detected all
> schedulers are triggered, not just the one configured for the
> particular svn repository.

This is a shortcoming of the current buildbot architecture.  The only
workaround I know is to run multiple buildmaster processes.  That's
what we do.  I've been toying with the idea of running multiple
BuildMaster services inside a single application (by futzing with the
buildbot.tac), but that's a pretty awful hack, and still requires each
slave machine to run a buildslave instance for each buildmaster.

We're about to add a half-dozen additional buildmasters, and each
buildmaster process already has a virtual size of 0.5G, so I'm a
little worried about this issue, too :)

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com