[Buildbot-devel] slave state able to cause buildstep creation?

[Ian Peters-Campbell]

Dynamic creation of steps isn't possible, but don't sell yourself too short
Dustin.  You can write a custom build step that has some  logic in its
__init__ and/or start methods that would behave differently based on the
output of the last step (as you said, with SetProperty.)  It's certainly
more work to write custom build steps, and it wouldn't be 100% dynamic (you
would have to have some limited set of choices).

It would be relatively straightforward, for instance, to have steps

PreBuild
BuildOne
BuildTwo

where PreBuild sets some property shouldBuildOne as a property and then
buildOne early outs if !shouldBuildOne and BuildTwo early outs if
shouldBuildOne.

I think you could put more flow logic into a single build step, but that
simple example could work for a lot of simple cases.

Ian



On Thu, Jun 25, 2009 at 9:25 AM, Dustin J. Mitchell <dustin at zmanda.com>wrote:

> On Thu, Jun 25, 2009 at 11:32 AM, Mike Winter
> (miwinter)<miwinter at cisco.com> wrote:
> > The reason I cant do the find and run in the single step is I want
> > granularity and visibility at the level indicated i.e. a cell per
> > runner.sh.
>
> This is going to be hard -- buildsteps are defined at config time, and
> are fixed for a builder -- you can't define specific buildsteps for a
> specific build.
>
> Note that you *can* capture the output of 'find' into a property
> (SetProperty) and then use that in a subsequent step.  But dynamic
> creation of steps is not possible.
>
> Dustin
>
> --
> Open Source Storage Engineer
> http://www.zmanda.com
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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/20090625/28e41691/attachment.html>