[Buildbot-devel] PBChangeSource and multiple repos in one instance

Wolfgang Rosenauer wolfgang at rosenauer.org
Tue Jan 8 08:30:46 UTC 2008


Shaun McDonald wrote:

> I'm not sure if this will help
> c['schedulers'] = []
> c['schedulers'].append(AnyBranchScheduler(name="all", branches=None, 
> treeStableTimer=5400, builderNames=["Mac-x86", "edgy-jdk"]))
>  From our OpenOffice.org buildbot here is some examples:
> http://ootermite.googlecode.com/svn/branches/076upgrade/buildmaster/production.cfg 
> which is referenced from the main master config:
> http://ootermite.googlecode.com/svn/branches/076upgrade/buildmaster/master.cfg 
> In the above line of code you would change the branches and the builder 
> names to the appropriate values. You would have multiple 
> AnyBranchSchedulers. We are currently using a custom CVS mail parser.

I'm not sure if that helps. Currently I added the new build to
c['schedulers'].append(Scheduler(name="development", branch="trunk",

But as I wrote, win-development and new-build are using different repos:
win-development: foo/bar/trunk
new-build:       foo/bar/baz/trunk

So what happens currently is that changes to foo/bar/trunk trigger a 
build of new-build (and win-development) and changes to 
foo/bar/baz/trunk trigger nothing :-(
That's where I'm not sure if buildbot can handle that at all or if 
svn_buildbot.py is notifying buildbot the "wrong" way.

>> I'm just trying to set up a new builder within an already existing
>> instance of buildbot.
>> It should check out and build another part of the repo.
>> I've added the builder to the Scheduler but I'm not sure if that
>> configuration is supposed to work since actually these are different
>> schedulers as I'd expect since for the one "trunk" is not really the
>> other "trunk" since both are based on different baseURLs.
>> If that config is supposed to work it seems we hit a different issue
>> with svn_buildbot.py since we are not sure how to call svn_buildbot.py
>> in that case.
>> The repo structure is like the following:
>> 1. repo: foo/bar/trunk
>> 2. repo: foo/bar/baz/trunk
>> We are not quite sure how to setup the commit hook for that 
>> configuration.
>> Any ideas?

More information about the devel mailing list