[Buildbot-devel] configuration help

Nathaniel Smith njs at pobox.com
Sat Nov 26 05:20:35 UTC 2005

On Fri, Nov 25, 2005 at 02:13:15PM -0800, Brian Warner wrote:
> > Documentation suggests that a single change set can only be associated with
> > a single branch. Is that correct ?
> Yes. "One branch per Change" is a pretty fundamental concept in the buildbot
> architecture, so I'm more willing to have the branch-determination happen in
> a new place than to try and change the buildbot to accomodate some crazy
> notion of multiple-branch Changes.

Monotone actually has multiple-branch changes too, but perhaps in a
much more sane way -- it's not like SVN where half of one change can
be in one branch, half in another, it's that each whole-project tree
snapshot has a list of branches associated with it.  Usually this list
is exactly 1 item long, but there are exceptions.

I haven't had a chance to look at the fancy new branch stuff in
buildbot yet, though, so I don't have any particularly useful stuff to
say about this.  If I was just hacking something up to get things
working, I'd probably just have the repo watcher deliver multiple
Changes and get on with life... ;-)

-- Nathaniel

"Of course, the entire effort is to put oneself
 Outside the ordinary range
 Of what are called statistics."
  -- Stephan Spender

More information about the devel mailing list