[Buildbot-devel] Stopping a Build Upon Output

Grig Gheorghiu grig at agilistas.org
Mon Oct 9 15:08:42 UTC 2006

On 10/8/06, brett <bneely at gmail.com> wrote:
> On 10/7/06, Roy S. Rapoport <buildbot-devel at ols.inorganic.org> wrote:
> > My builds have update,build, and test phases (in that order).  The tests
> > take a while -- in one case, 4206 seconds.
> >
> > Now, a build may actually conclude with no changes (because nothing has
> > had to be rebuilt).  I would love to find a way to:
> > A) Based on output from a build step, determine this has happened; and
> > B) When it happens, skip doing the tests.  This isn't a 'haltOnFailure'
> > situation -- if it happens, we're all good and we want to say we're
> > successful.
> Roy:
> Rather than have buildbot execute your tests directly, have the test
> phase call a script of your own that tests for your precondition, and
> then optionally executes the command to run the tests.
> It seems possible to modify the output of each phase on the waterfall
> display (e.g. http://build.webkit.org/), so your output could specify
> whether or not the tests ran and why.  I don't know how to do that
> though.
> -b

Here's one way I found to dynamically update the status text for build


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20061009/fa343dff/attachment.html>

More information about the devel mailing list