[Buildbot-devel] Pure local builders

Al Nikolov a.nikolov at drweb.com
Wed Apr 22 14:08:22 UTC 2009

Brad Hards wrote:

>> To run other things remote. See my example in starting thread message. I
>> use one (pure local) builder to orchestrate several (usual) builders.
> Your original example was a bit light on for what you are actually trying
> to do, so this might not be too good:

I see what was unclear in my example. builder.1, builder.2, builder.3 are
steps 1, 2, 3 of one builder

> * Pure local aggregate builder.1: Set aggregate build unique ID.
> MasterShellCommand can do this
> * Pure local aggregate builder.2: Trigger aggregate scheduler and wait.
> There are a range of scheduler options. Not clear why you need a builder
> for this.
> * Pure local aggregate builder.3: Publish artefacts tagged with BUID under
> one common build number.
> Again, a MasterShellCommand could do this.

So you have three steps of one pure local builder (it doesn't execute any
remote code). Having a dedicated "local" buildslave for such builders which
doesn't execute any code sounds like overkill. (In fact, i agree, it isn't
an overkill from the POV of system resources, it's more like
must-be-generalized of the BuildBot concept).

More information about the devel mailing list