public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Postgresql Hackers <[email protected]>
Subject: Re: Build farm
Date: Thu, 20 Nov 2003 00:42:58 +0100 (CET)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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 [email protected]
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: <[email protected]>
* 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