Ticket #244 (new enhancement)
Add ability to trigger on more than one svn path
|Reported by:||jeberger@…||Owned by:||cmlenz|
|Keywords:||Cc:||thomas.moschny@…, osimons, trac@…, sahendrickson@…, cboos, leandor@…, felix.schwarz@…, myroslav@…, kroman0@…|
It would be nice to add the ability to trigger a build based on more than one svn path. The build would then use the most recent revision in which at least one of the watched paths was modified.
We're using svn+Trac+Bitten to build Linux-based firmwares for our products. Our system is based on a solution similar to the Gentoo emerge system:
- There is a set of package descriptors that describe dependencies and build recipes. Every developer has a complete copy of all the descriptors on their computers;
- And there is a source repository where the actual package sources reside. When a developper wants to work on a given package, he only needs to check out the source for this package alone.
Our svn repository is therefore separated into two distinct repositories (actually, two distinct trees in the same repository):
- A repository for the sources;
- A repository for the package descriptors.
At present, Bitten triggers a rebuild when the sources are modified, but it ignores changes to the package descriptors. It would be nice if we could have Bitten watch both the path to the source and the path to the descriptors (an possibly the paths to the more important dependencies) and trigger a build whenever one of them changes.