[Buildbot-devel] Send only one mail even when several builds fail

[tom fogal]

"Dustin J. Mitchell" <dustin at v.igoro.us> writes:
> On Sun, Oct 24, 2010 at 6:37 PM, tom fogal <tfogal at sci.utah.edu> wrote:
> > Well, what is the right approach then? This is annoying for us as
> > well.
>
> We should have a general queueing-system style system against which
> notification clients can query.
>
> The more I think about it, the more I think that we need to use a
> real message-queueing system in Buildbot.

But then the notification client needs the knowledge of which things to
aggregate.  For example, in my case, I need to code such a notification
agent to find the results of win32, osuse, ubuntu, rhel, and debian
builders.

The aggregation information is already *in* my master config, by way of
schedulers.  If I have to configure it somewhere else, they're going to
get out of sync.

Even worse, some builder might not finish, or even start -- e.g.
my osuse machine loses its net connection or something, the slave
disconnects.. and then my client, which is waiting for all such
builders to finish, just locks.  We could solve this by adding a way to
query if slaves are up, but then I have to *do* that.

Querying of slave status and handling errors like disconnect is painful
and error prone with a pull-style system, but since the buildmaster
is already handling slaves, it can easily do these things in a a
push-style manner.

-tom