[Buildbot-devel] BuildBot master configuration questions

[Evan Driscoll]

I have two questions, both with a somewhat similar flavor, and both 
related to this sentence in the section on change sources: "In general, 
each Buildmaster watches a single source tree. It is possible to work 
around this, but true support for multi-tree builds remains elusive."


1. If I have multiple projects (e.g. I decide to build them based on
    different criteria, and perform different actions to build them),
    would I save a lot of headaches by making multiple masters?

    Difficulty: I'd like to share build slave machines between the
    masters for better load balancing. At the extreme, for the time
    being we will only have one machine acting as a build slave.
    Should I just run multiple slave instances on that machine, one
    per master?


2. Suppose I have one project that is made up of several repositories.
    How should I configure things? (To keep things simple I'd like to
    use either (probably multiple instances of) the SVNPoller class or
    the svn_watcher contrib script.)

    To be specific, this project has a few libraries that are in
    separate repositories, so to build it, you have to check all of them
    out. We also want to watch all of those repositories for changes and
    to make blamelists.

    (Actually I have two of these projects. For one, there is an
    umbrella repository that uses svn:externals to pull all the
    different parts in, so if that makes the situation easier it'd be
    nice to know that too. The second project doesn't really have that
    option.)

Evan