Re: buildfarm notifications

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: buildfarm notifications
Date: 2005-06-19 18:49:57
Message-ID: 42B5BE55.6020401@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Josh Berkus wrote:

>Andrew,
>
>
>
>>If people don't monitor the buildfarm then it isn't serving its purpose
>>of catching these things quickly.
>>
>>
>
>Related to that , Spikesource has started their automated tests (which
>currently include JDBC, php and phpPgAdmin as well as PostgreSQL). They have
>a web services interface; I was thinking of writing a widget which would
>e-mail notices of failures. Maybe I should send them to your list so that
>it's all one digest?
>
>
>

Er, who?

What are they testing and how? How often?

I am expecting that for the most part people will want the lists of
state changes, rather than the lists of all builds or failures. Will
Spikesource tests track state changes?

BTW, these list are being set up only for announcements, so I would have
to grant permission before any results started flowing.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2005-06-19 19:03:38 Re: [PATCHES] default database creation with initdb
Previous Message Tom Lane 2005-06-19 18:06:21 Re: Checkpointing problem with new buffer mgr.

Browse pgsql-patches by date

  From Date Subject
Next Message Josh Berkus 2005-06-19 19:42:56 Re: buildfarm notifications
Previous Message Josh Berkus 2005-06-19 17:09:36 Re: [PATCHES] default database creation with initdb