[Buildbot-devel] multiple schedulers/changesources

Wolfgang Rosenauer wolfgang at rosenauer.org
Thu Oct 9 07:07:27 UTC 2008

Charles Lepple schrieb:
> On Wed, Oct 1, 2008 at 6:38 AM, Wolfgang Rosenauer
> <wolfgang at rosenauer.org> wrote:
>> Hi,
>> I'm wondering if it's possible to have different projects in one
>> buildbot instance like this:
>> I get my changes notifications from svn using PBChangeSource but I have
>> different projects in the config which have different baseURLs obviously.
>> So I tried to define two AnyBranchSchedulers instead of one but that's
>> not enough apparently.
>> So I guess incoming changes always trigger all schedulers if they
>> contain the defined branch names which are defined to be monitored by
>> the AnyBranchScheduler?
>> Any other solution besides having another master instance?
> Definitely - use the fileIsImportant argument to the scheduler, and
> make your fileIsImportant function filter based on the "branch" (SVN
> path).
> [...]
> change.branch can be None if the default branch is being built;
> otherwise, I believe it is a string.

I've played around with that but I still haven't got it working :-(
The branch is either the real branch (if $REPOS in the notifier is the
base) or it seems to be always "trunk" if it's higher level change in
the tree structure. In the latter case I can filter on change.files and
can see some part of the svn path but in the first case I can't it seems.

So I'm filtering on change.files now but have to live with the fact that
one project can't use the AnyBranchScheduler because it only sees
"trunk" changes in every case.

Thanks for the hint anyway,

More information about the devel mailing list