[Buildbot-devel] Master Shell Command exist status does not affect overall build status

[Amber Yust]

Have you tried setting flunkOnFailure=True in the MasterShellCommand
arguments?

~Amber

On Sat, Jan 1, 2011 at 9:33 AM, <ariasgore at gmx.de> wrote:

> Hello,
>
> One of my buildslaves performs a couple of additional MasterShellCommands
> (output post processing)
> Sometimes these steps fail and in the single build view they are marked as
> red but the overall status of the slave's build process remains green.
> I would suggest to make it configurable since the master shell command is
> important for the buildslave status too (at least for my purpose) and I
> therefore need to check always the waterfall to see if all single steps were
> run successfully.
>
> Buildbot 0.8.3
>
> Thanks
> Sam
> --
> Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
> belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
>
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment,
> and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> 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/20110101/cc93d0d1/attachment.html>