buildfarm notifications

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: buildfarm notifications
Date: 2005-06-18 20:57:33
Message-ID: 42B48ABD.6020605@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


[from 2pc post mortem thread on -patches]

Stefan Kaltenbrunner wrote:

>>Looks suspicious, doesn't it. How long since you last tested on that
>>machine?
>>
>>
>
>*argl* - it's not 2PC ...
>
>the machine had some issues a week ago or so - but it looks like the
>problem occured first here:
>
>http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2005-06-15%2023:50:04
>
>and in that changeset we have some timezone-patches ...
>
>
>
>
>

If people don't monitor the buildfarm then it isn't serving its purpose
of catching these things quickly. To aid that process I am currently
working on a notification enhancement for buildfarm which has long been
requested. Here's the description I sent to the buildfarm list (the
first few lines refer to how buildfarm members would have themselves
notified - non-buildfarm members can ignore):

> Basically, it would work thus:
>
> in your config file, put a setting like this:
>
> mail_events => { all=> ['me(at)foo(dot)bar(dot)com', 'him(at)baz(dot)blurfl(dot)com'}],
> failures => 'bzzt(at)my(dot)alarm(dot)com' },
>
> The allowed event keys in this hash would be:
> all: every build status received
> failures: every non-OK build status received
> all_changes: every time status changes
> green_changes: every time status changes to/from OK
>
> The corresponding values in the hash can be an arrayref of email
> addresses, or a single scalar email address.
>
> The notification sent by the server would look something like this:
>
> ----------------
> Subject: PGBuildfarm member <membername> Branch <branchname> Status
> [changed to] <status>
>
> The PGBbuildfarm member <membername> had the following event on branch
> <branch>:
>
> Status: <status> (or Status Change from <oldstatus> to <newstatus>)
>
> The snapshot timestamp for the build that triggered this notification
> is: <YYYY-MM-DD HH::mm::ss>
>
> The specs of this machine are:
> OS: <osname> <osversion>
> Arch: <architecture>
> Comp: <compiler> <compiler-version>
>
> For more information, see
> http://www.pgbuildfarm.org/cgi-bin/show_history.pl?nm=<name>&br=<branch>
>
> ----------------------
>
> In addition, I am thinking of setting up mailing lists that digest all
> these event sets for all members over a 24 hour period, and that
> anyone can subscribe to.

The enhancement is almost done, and the whole thing will be complete
this weekend, I hope.

The mailing lists are being set up as digest-only, at least for the all
and failures lists - the state change lists should have much lower
volume, and I will probably make them digest optional.

comments welcome (buildfarm exists to help people on this list - if you
want something speak up).

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2005-06-18 21:43:46 Re: Post-mortem: final 2PC patch
Previous Message Tom Lane 2005-06-18 20:38:29 Re: Checkpointing problem with new buffer mgr.

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2005-06-18 21:43:46 Re: Post-mortem: final 2PC patch
Previous Message Michael Fuhr 2005-06-18 20:00:14 Typo in pl_funcs.c comment