[Buildbot-devel] AnyBranchScheduler and builder's builddir parameter

Dustin J. Mitchell dustin at zmanda.com
Sun Sep 30 22:04:37 UTC 2007

On 9/30/07, Sergey A. Lipnevich <sergey at optimaltec.com> wrote:
> Thanks Dustin, I think I'll follow your advice! The reason why I wanted
> this feature was the multitude of sub-projects (dozens), branches (at
> least a couple of versions plus trunk per each sub-project), and kinds
> of build (normal, packaging, etc.) that I have to deal with. But I can
> see that if I make a single builder for all sub-projects, it's going to
> look inconclusive on the waterfall: if the build is successful, it won't
> mean that all my dozens of projects have been built successfully, it's
> only the last one to build that was good. So, I think I have to bite the
> bullet and create as many builders as I have sub-projects.

This is one of the many failings of the waterfall display -- it's good
for debugging buildbot, but not so good for seeing what's been built.
The grid display (which will hopefully be in 0.7.7) will do a better

> My repository structure is {sub-project}/trunk|branches|tags/{version if
> not trunk}. I'm looking at going into Subversion repository, doing "svn
> ls" at the top level, and creating builders for each directory I find.
> Is that a good approach?

>From master.cfg?  Sounds good -- although I'm not entirely sure how
well the 'reconfig' will work in that case -- you may have to make a
point of always restarting the master when the list of projects


Storage Software Engineer

More information about the devel mailing list