X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 441D5D1D587 for ; Tue, 18 Nov 2003 22:12:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 29278-02 for ; Tue, 18 Nov 2003 18:12:29 -0400 (AST) Received: from bramble.mmrd.com (unknown [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id 74917D1D5A4 for ; Tue, 18 Nov 2003 18:12:26 -0400 (AST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by bramble.mmrd.com (8.12.8/8.12.8) with ESMTP id hAILIecM016549; Tue, 18 Nov 2003 16:18:40 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id hAIMCQl06243; Tue, 18 Nov 2003 17:12:26 -0500 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id V3JR42AH; Tue, 18 Nov 2003 17:12:24 -0500 Subject: Re: Build farm From: Robert Treat To: Andrew Dunstan Cc: Postgresql Hackers In-Reply-To: <3FBA74B7.2090106@dunslane.net> References: <87smkmgyn7.fsf@mailbox.samurai.com> <20031117233828.Y731@ganymede.hub.org> <200311180942.31093.josh@agliodbs.com> <3FBA6999.9030906@dunslane.net> <20031118151211.U731@ganymede.hub.org> <3FBA74B7.2090106@dunslane.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 18 Nov 2003 17:12:26 -0500 Message-Id: <1069193546.10333.7726.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/1016 X-Sequence-Number: 47304 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