[Buildbot-devel] configuration help

[Stefan Seefeld]

Brian Warner wrote:

> Hmm. So far I've been assuming that repository branch policy is part of the
> repository, not part of the buildbot, but I can see how it would be more
> convenient to be able to specify it inside the master.cfg file. While working
> on the build-on-branch feature, I started at the end (on the buildslaves) and
> worked my way back "upstream" towards the ChangeSources. Therefore I was able
> to keep putting off the decision about where the branch names come from in
> the first place. This issue of whether branches are calculated inside the
> ChangeSource or back in the sender (svn_buildbot.py) is a reflection of this
> deferred architecture decision (i.e., of my laziness :).

Documentation suggests that a single change set can only be associated with
a single branch. Is that correct ?
Given that subversion itself doesn't have any concept of a branch, and that
branches are almost arbitrarily associated with subdirectories, that would
suggest that the 'branch detection' mechanism we are discussing should indeed
happen inside svn_buildbot.py, so it can then generate one notification
per branch, even for a single checkin / revision.

I agree with Chris that a little configuration file to do that would be
nice, though I would choose a more pythonic approach. ;-)


Regards,
		Stefan