[Buildbot-devel] Status of Multi-Project Support

[Steve James]

On Wednesday 06 August 2008, Mark Melvin wrote:
> Hi There,
>
> I'm looking at writing a build system for our internal product builds
> and in addition to being a huge Python fan, I have been looking pretty
> hard at Buildbot and it is almost everything I would sit down and
> think about writing myself.  However - there seems to be a recurring
> issue with people wanting to build more than one "project",
> additionally complicated by the fact that these projects may be
> interdependent (i.e. the output of one project is involved in the
> build of another).
>
> I was wondering what the status of this was?  Does buildbot now
> support this workflow in some undocumented way, have people hacked it
> to suit their needs, or do people just not use it this way at all?

What a good question. I'd also like know what the established lore is on this 
too. Wouldn't this be an ideal wiki topic? Is it an FAQ even?

FWIW, I recently tried out a Buildbot configuration for our established builds 
here, currently based on Test::AutoBuild. The first obstacle is the 
assumption that there is only one source repository. Fortunately there's a 
patch for multiple Subversion repository support so I continued. The next 
obstacle was defining dependencies such that if A or B is changed A or B 
re-builds but _also_ that B rebuilds is A rebuilds, and so on. Amazingly (to 
me at least) I hacked up a new kind of scheduler that does just what I want. 
The experiment continues, but so far it looks like I can get all the benefits 
of Buildbot _and_ continue to build interdependant projects with it. Yay!

Steve.


-- 
You shall be rewarded for a dastardly deed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://buildbot.net/pipermail/devel/attachments/20080806/3002e00a/attachment.bin>