Ticket #467 (closed enhancement: fixed)
SVN - allow multiple repositories
|Reported by:||ipv6guru||Owned by:||mue|
|Cc:||daniel@…, duncan_j_ferguson@…, chris.bainbridge@…|
Our project is divided into various components, some of which are spread over multiple different subversion repositories. Many of these components eventually assemble into a single project, so having multiple buildmasters didn't really make much sense for us. We wanted to be able to trigger a different set of builders depending on in which repository a commit was made.
This patch allows a scheduler to specify a "repository" parameter, in much the same way as the existing branch parameter. If the parameter is not "None" the scheduler will filter out changes that are not sent with a matching repository.
The subversion change sender is modified to transmit the repository value across to the ChangeSource and the Change itself has a "repository" field added to it.
An example from our master.cfg of a scheduler that only wants to wake up when a change is from a certain repository:
cschedulers?.append(Scheduler(name="foundationmunged-sched", repository="/data/svn/foundationmunged", branch=None, treeStableTimer=1*5, builderNames=["foundationmunged-linux", "foundationmunged-mac"]))
Note that "repository" is a required argument and must be specified as "None" if you want to wake up on a change to any (or unspecified) repositories. This is done to be consistent with the way that "branch" is being handled; it would be easy to make the repository field optional if that is preferable.
- Owner set to mue
- Status changed from new to assigned
- Type changed from defect to enhancement
comment:29 Changed 3 years ago by dustin
- Status changed from assigned to closed
- Resolution set to fixed
- Milestone changed from 0.8.+ to 0.8.0