[Buildbot-devel] BuildBot master configuration questions

[Fulvio Cervone]

Not sure to which extent the multiple projects are not supported...actually I have a single builder that pokes in my server, checking out multiple projects and building them without problems; I have only one master and one slave and 5 different projects.

They are all on the same server thou, maybe the limitation is when you use multiple servers to get the source code and build?

Using multiple masters on the same slave will bring you nothing but problems; the architecture is designed to work in the other way (multiple slaves and one master); if you really need to have balancing you can make 2 servers, each one that runs his own instance of master and slave on the same machine, but this would not solve the balance problem completely thou.

perhaps you could make different builders that does the same thing, and set them to be triggered at different times; but still you will run only one build process at time (unless you set parallels build; never tried so I do not know how good it works).

Regarding point #2, you could basically do what i did: check out a project in a step, build it in another step, check out the second project and build it and so on; using the order that best suit your product (mine requires 2 other components to be built before the main one, and each one is in it's own repository).

Then depends how you wanna control the process...you could make a builder for each, and once that all the required components are built you can trigger the main one; or have everything in a single builder....I do not think that there is a right or wrong way since it depends from your project.



On May 12, 2011, at 11:05 AM, Evan Driscoll wrote:

> 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
> 
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel