[Buildbot-devel] Buildbot newbie question on complex setup

Richard Offer richard at whitequeen.com
Sat Apr 28 19:06:54 UTC 2012

I'm researching replacing our multi-agent Bamboo CI server with a more integrated solution.

I've looked at Jenkins and am now evaluating Buildbot.

Its starts of well since I much prefer to write code to do something than click in a web browser :-)

But I'm missing the bit that goes from a simple configuration to a complex one.

Here's what I have so far:

	One build factory for each configuration (linux32, linux64, windows)

But this is what I need to piece together

	the linux64 build is product master package
	the linux32 and windows (on dedicated slaves) builds need to build and their results (RPMs, MSIs) need to be passed to the linux64 build factory
	the linux64 build then needs to start a final job on another agent (running VMware Studio) to take all the pieces and package them into an OVF.

Obviously the linux32 and windows builds should be in a BuildSet - but I can leave that for now…

What is the best way to share "artifacts" between the various build factories ?

I've looked at the trigger scheduler - but am trying to work out how to use it between different factories - I think I want to "shell out" an entire BuildFactory - not one step at a time…

It would also be nice if I could attach an environment to a build slave - since then I could share build factories across different slaves ( Linux32 and darwin only differ in their environments)



More information about the devel mailing list