[Buildbot-devel] multiple subversion repositories
Mark <line72> Dillavou
mlists at line72.net
Tue Jan 24 13:21:54 UTC 2006
On Mon, 2006-01-23 at 15:15 -0800, Brian Warner wrote:
> To handle completely separate subprojects, you need something else. I'd
> suggest making a subclass of Scheduler which completely ignores the Changes
> that occur on the wrong subproject, rather than merely marking them as
> unimportant. You'd do this in the addChange() method, by simply returning
> without doing anything if the change is not a part of the subproject you're
> handling. You'll have two such Schedulers, one for each subproject. Each
> Scheduler would then trigger its own Builder, just as you were doing before.
I will look into this.
> Is there any particular reason you want both projects to be handled by the
> same buildmaster? It may be the case that the projects are better served by
> separate buildmaster instances. Our multiple-subproject support isn't very
> strong right now, but to figure out what needs to be done to improve it, it
> would help me to understand what your motivations.. are the subprojects being
> combined together somehow? Are there buildsteps which use source code from
> both projects together at some point? Or is it just a reporting convenience,
> having one web page instead of two?
My two projects rely on each other (one is the library and the other is
the app). And since the app relies on the latest version of the
library, I need locks between the two projects so that app doesn't get
built until the latest version of the library is done building. I was
using two buildmasters before, and the app would have a symlink to the
libraries build project, but a lot of times a developer will commit
changes to the library then immediately to the app, and the app will
fail because the library hasn't finished building.
More information about the devel