Re: [Pgbuildfarm-members] Buildfarm alarms - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: [Pgbuildfarm-members] Buildfarm alarms
Date
Msg-id 20060927201020.GR19827@nasby.net
Whole thread Raw
In response to Re: Buildfarm alarms  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [Pgbuildfarm-members] Buildfarm alarms  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Wed, Sep 27, 2006 at 01:55:21PM -0400, Andrew Dunstan wrote:
> Kris Jurka wrote:
> >
> >
> > On Wed, 27 Sep 2006, Andrew Dunstan wrote:
> >
> >> The settings are in hours, so this says that if we haven't seen  a 
> >> HEAD build in 1 day or a stable branch build in 1 week, alert the 
> >> owner by email, and keep repeating the alert in each case every 2 days.
> >>
> >
> > How does this know if there wasn't a build because nothing in CVS 
> > changed over that time period?  Especially on the back branches it is 
> > normal to go weeks without a build.
> >
> > Kris Jurka
> >
> 
> Indeed. The short answer is it doesn't. But there is a buildfarm config 
> option to allow you to force a build every so often even if there hasn't 
> been a CVS change, and I'm thinking of providing an option for this to 
> be branch specific. The you would make this setting shorter than your 
> alarm period for any branch you had an alarm set for.

Another possibility is just having the client report "no CVS changes
detected" to the server, as a form of a ping.
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


pgsql-hackers by date:

Previous
From: Thomas Hallgren
Date:
Subject: Re: [PATCHES] Patch for UUID datatype (beta)
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Restart after power outage: createdb