[Buildbot-devel] Multiple sources and build machines

Nick Trout nick at rockstarvancouver.com
Tue Jun 14 16:01:21 UTC 2005

I'm just wondering what the best way to set up the following scenario
is. I have a p4 server (so p4Poller for changes). 

I want to have one master buildbot which controls 3 slaves. 1 slave
builds application versions. 1 slave processes data. 1 slave builds
debug/stats version of application to give feedback etc. When part of
the source tree changes I want to build the application, and when
another part of the tree changes I want to compile data. I don't want to
have to compile the application or data where I don't have to. How might
I go about setting this up? There appear to be a couple of solutions:

a) when the source notifies us of a change we somehow get the change
information (perhaps a dummy step?) and then decided whether we want to
make a build or not. Doesn't seem like a particularly good way to go as
well start a build and then abort it if we don't want to do anything.

b) we could attach a source to a builder so that the builder is notified
when the source changes. This seems to make more sense. I can't see how
I would attach a source to a builder, the source appears to be part of
the master. Perhaps this could be changed so that the default behaviour
is changes are attached to the master and all source notifications cause
a build to kick off, but sources can optionally be attached to builders
so that multiple projects could be spawned from the same master.

c) I run multiple masters and have a slave hanging off each. Kind of
defeats the whole point of using BB though (i.e. having all the status
info available on one machine).

It seems like b) is the best solution. If sources were named it would be
fairly easy to just add one to a builder config.

Thoughts? Thanks,


More information about the devel mailing list