[Buildbot-devel] can i reuse BuildSteps?

[Axel Hecht]

Each build (not even builder or build factory) get's its own instance of
your buildstep. There is some magic to work around master.cfg's still
passing instances of build steps. But in general, what you'd specify, and
what happens in the background no matter which is:

master.cfg (or the build factory) specify a step factory, commonly created
by a step class and constructor arguments. For each new build, the step
factory creates a new step object.

After clarifying that, yes, you can share the step factories between
builders.

Axel

2008/12/1 Sebastian Kuzminsky <seb at highlab.com>

> I've got a half-dozen BuildFactories, each used by a couple of Builders.
>   In the beginning I ran all the buildslaves, but now we're starting to
> have random developers volunteer to run slaves.  I want to add a
> BuildStep to the beginning of each of my factories to show the
> configuration that the buildslave is running with (gcc version, kernel
> version, etc).
>
> Is it allowed to create a single BuildStep to determine this and add
> that one BuildStep to the beginning of each of my existing
> BuildFactories, or do I need to create a separate (identical) BuildStep
> instance for each BuildFactory instance?
>
>
> --
> Sebastian Kuzminsky
> One of my most productive days was throwing away 1000 lines of code.
>     -- Ken Thompson
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20081201/425d4c31/attachment.html>