public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Postgresql Hackers <[email protected]>
Subject: Re: Build farm
Date: 18 Nov 2003 17:12:26 -0500
Message-ID: <1069193546.10333.7726.camel@camel> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Tue, 2003-11-18 at 14:36, Andrew Dunstan wrote:
> Marc G. Fournier wrote:
> 
> >On Tue, 18 Nov 2003, Andrew Dunstan wrote:
> >
> >  
> >
> >>Maybe some sort of automated distributed build farm would be a good
> >>idea. Check out http://build.samba.org/about.html to see how samba does
> >>it (much lighter than the Mozilla tinderbox approach).
> >>
> >>We wouldn't need to be as intensive as they appear to be - maybe a once
> >>or twice a day download and test run would do the trick, but it could
> >>pick up lots of breakage fairly quickly.
> >>
> >>That is not to say that more intensive testing isn't also needed on
> >>occasion.
> >>    
> >>
> >
> >Check the archives on this, as its been hashed out already once at least
> >... I think the big issue/problem is that nobody seems able (or wants) to
> >come up with a script that could be setup in cron on machines to do this
> >... something simple that would dump the output to a log file and, if
> >regression tests failed, email'd the machine owner that it needs to be
> >checked would do, I would think ...
> >
> 
> If there's general interest I'll try to cook something up. (This kind of stuff is right up my alley). I'd prefer some automated display of results, though. A simple CGI script should be all that's required for that.
> 

look in the tools directory of cvs, i swear Bruce checked in a script he
uses for similar tasks..

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

view thread (83+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Build farm
  In-Reply-To: <1069193546.10333.7726.camel@camel>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox