[Buildbot-devel] Splitting slave from master

Greg Ward greg at gerg.ca
Sat Jun 5 16:17:51 UTC 2010

On Fri, Jun 4, 2010 at 10:39 PM, Dustin J. Mitchell <dustin at zmanda.com> wrote:
> I just opened bug 880 (http://buildbot.net/trac/ticket/880) to split
> the slave and the master into separate packages.  This has a bunch of
> advantages:
> 1. slave doesn't require Jinja and SQLite
> 2. slave is a much smaller install
> 3. slave can run on a wider variety of systems (e.g., Cygwin)
> I'm not entirely sure what the best way to manage a multi-package
> Python project is, though - if you know of any other projects that
> have multiple packages, please point me to them as an example!

Mercurial has two top-level packages, 'mercurial' and 'hgext'.  Works
just fine.  I know for sure that distutils doesn't care.  Neither does
Python, nor RPM nor dpkg nor any other software that you're likely to

But why not just keep everything under 'buildbot', and make sure that
everything needed exclusively on the slave is in 'buildbot.slave'?
Maybe create 'buildbot.common' for shared code that has to be on both
master and slave.  There's really no requirement for multiple
top-level packages.


More information about the devel mailing list