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

Wolfgang Rosenauer wolfgang at rosenauer.org
Wed Jan 9 10:31:13 UTC 2008

Shaun McDonald wrote:
> On 8 Jan 2008, at 08:30, Wolfgang Rosenauer wrote:
>> c['schedulers'].append(Scheduler(name="development", branch="trunk",
>>                                 treeStableTimer=15,
>>                                 builderNames=["win-development",
>>                                 "new-build"]))
> You will need to have two of the above, one for each of the builders. 
> The branch will be baz/trunk for the other one.
>> 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.
> You should also have two c['change_source'] = items, or maybe the 
> buildbot only has support for one change source. In which case you will 
> need to have multiple masters. It would be confusing to have a master 
> where the salves work off different source trees.

I gave up on it and configured another master. I wanted to avoid that 
since all the builders are the same anyway and it creates a bit more 
maintenance overhead.

Thanks anyway,

More information about the devel mailing list