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

Sergey A. Lipnevich sergey at optimaltec.com
Sun Sep 30 21:22:22 UTC 2007

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.

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?

Thank you!

Dustin J. Mitchell wrote:
> On 9/27/07, Sergey A. Lipnevich <sergey at optimaltec.com> wrote:
>> I'm looking at creating a custom build factory with all necessary steps
>> anyway, but I was hoping that maybe there is per-branch checkout in
>> steps.source.SVN, since there is per-branch scheduling in
>> AnyBranchScheduler :-).
> I don't believe such a thing exists, but it would be fairly
> straightforward to add -- and submit the patch back to buildbot.
> I'm not sure why you'd want to do this, though -- do you want to
> preserve the "most recent" build of each branch on each builder?
> My solution was to run a different builder for each branch -- but
> that's to allow concurrency, not keep directories around.
> Dustin

More information about the devel mailing list