[Buildbot-devel] Syncing multiple builders and notifications

[Amber Yust]

Hm. It's kind of a hack, but you could have a third builder for which the
only step is a Trigger step, whose job it is to trigger the other two
builders (changing them to Triggerable schedulers), and have that trigger
step wait for the triggered builds to complete (via waitForFinish=True)?
Then have the success email based off of whether the *trigger* step finishes
successfully (since it will fail if any of its triggered builds failed).

~Amber

On Fri, Nov 5, 2010 at 6:11 AM, Gregory Bayard <gregory.bayard at gmail.com>wrote:

> Hello,
>
> I currently have a very simple buildbot running with two builders (a
> windows builder and linux builder) and two slaves (a windows server and a
> linux server).  I have two mail notifiers configured, one sends a success
> notification to the blamelist when a build completes and the other sends a
> failure notification to a distribution list.  Currently the success
> notification is triggered twice, once for each build's completion and if you
> break one build and not the other you will receive both a success and a
> failure notification.  What is the best way to configure buildbot so that
> the success notification will only be generated when both builders complete
> successfully so that only one success will be sent and if only one build
> succeeds no success notification will be sent?
>
> Thanks,
> Greg
>
>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
> _______________________________________________
> 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/20101105/133dc876/attachment.html>