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 3D5CFD1B515 for ; Wed, 19 Nov 2003 23:43:12 +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 93055-04 for ; Wed, 19 Nov 2003 19:42:43 -0400 (AST) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id 6C2ECD1D452 for ; Wed, 19 Nov 2003 19:42:39 -0400 (AST) Received: (qmail 29135 invoked by uid 65534); 19 Nov 2003 23:42:40 -0000 Received: from dsl-082-082-166-244.arcor-ip.net (EHLO [192.168.2.136]) (82.82.166.244) by mail.gmx.net (mp023) with SMTP; 20 Nov 2003 00:42:40 +0100 X-Authenticated: #495269 Date: Thu, 20 Nov 2003 00:42:58 +0100 (CET) From: Peter Eisentraut X-X-Sender: peter@peter.localdomain To: Andrew Dunstan Cc: Postgresql Hackers Subject: Re: Build farm In-Reply-To: <3FBBC423.9000801@dunslane.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/1094 X-Sequence-Number: 47382 Andrew Dunstan writes: > Essentially what I have is something like this pseudocode: > > cvs update Be sure check past branches as well. > check if there really was an update and if not exit OK. > configure; get config.log Ideally, you'd try all possible option combinations for configure. Or at least enable everything. > make 2>&1 | make-filter >makelog > make check 2>&1 | check-filter > checklog You could also try out make distcheck. It tries out the complete build, installation, uninstallation, regression test, and distribution building. > (TBD) send config status, make status, check status, logfiles OK. > make distclean When I played around with this, always copied the CVS tree to a new directory and deleted that one at the end. That way, bugs in the clean procedure (known to happen) don't trip up the whole process. > The send piece will probably be a perl script using LWP and talking to a > CGI script. That will be the difficult part to organize, if it's supposed to be distributed and autonomous. -- Peter Eisentraut peter_e@gmx.net