[Buildbot-devel] Buildbot newbie question on complex setup
clepple at gmail.com
Sun Apr 29 18:27:36 UTC 2012
On Apr 29, 2012, at 1:46 PM, Dustin J. Mitchell wrote:
> On Sun, Apr 29, 2012 at 12:38 PM, Richard Offer <richard at whitequeen.com> wrote:
>> So I guess the question is now how to I trigger across build factories ? -
>> or are build factories a logical collection and I should be using triggers
>> between the build steps in two different factories ?
>> From your comments below it seems that using triggers between different
>> factories isn't supported in the current objects ?
> BuildFactories are just lists of steps, nothing more. So you can have
> a step in a builder trigger a scheduler which then starts an arbitrary
> number of other builders.
one of the keys here is that individual build steps can't call other build steps the way you might think of function calls in, say, C or Python. So a BuildFactory (and the resulting Build that happens at runtime) is always a linear sequence of steps.
The Trigger step , with its corresponding Triggerable scheduler, lets one build step call another sequence of steps (by referencing its builderName in the Triggerable configuration).
The example in the Triggerable documentation  uses "waitForFinish=True" to serialize all of the steps, but by adding several schedulers to the schedulerNames list, you can get your various platform builds to run in parallel.
clepple at gmail
More information about the devel