[Buildbot-devel] Multiple Builders or BuildSet?

Dustin J. Mitchell dustin at v.igoro.us
Thu Jan 24 02:07:35 UTC 2013


On Tue, Jan 22, 2013 at 5:44 PM, Kenny Ho <kenny.ho at ca.flextronics.com> wrote:
> I just started trying out BuildBot and I have some questions on setting up
> multiple targets on the same source tree.  From what I’ve learned so far, I
> figured I can make a builder for each target I want to build and then
> associate all the builders to a particular source change/scheduler, but then
> I will need to find a way to check the status of each build to do some kind
> of post build processing.  Then I came across BuildSet, which seems to be
> exactly what I need, but I couldn’t figure how it fit into the
> MasterBuilderConfig/master.cfg.  Does BuildSet actually work in that
> context?  If so, does anyone have an example?   Or must I extend my own
> scheduler in order to use it?  I have also saw a mention somewhere that the
> BuildSet feature will be removed in 0.9?
> (https://github.com/buildbot/buildbot/pull/483) Is that true?

Buildsets are an implementation detail of Buildbot, not something you
can configure directly.  They serve to group the build requests that a
scheduler makes in a single go.  A Dependent scheduler monitors
buildsets produced by its upstream scheduler, and initiates some
additional builds when each buildset completes.

You haven't said what sort of post-build processing you want to
perform, so it's hard to say much more than that.

> Legal Disclaimer:
> The information contained in this message may be privileged and
> confidential. It is intended to be read only by the individual or entity to
> whom it is addressed or by their designee. If the reader of this message is
> not the intended recipient, you are on notice that any distribution of this
> message, in any form, is strictly prohibited. If you have received this
> message in error, please immediately notify the sender and delete or destroy
> any copy of this message!

Seriously?  1995 called, and it wants its email server back..

Dustin




More information about the devel mailing list