Dave Page wrote:
>
>
>
>
>>-----Original Message-----
>>From: pgsql-hackers-owner@postgresql.org
>>[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of
>>Andrew Dunstan
>>Sent: 14 July 2005 13:35
>>To: Tom Lane
>>Cc: PostgreSQL-development
>>Subject: Re: [HACKERS] windows regression failure - prepared xacts
>>
>>
>>
>>ON a related note, we need more Windows boxes on the
>>buildfarm - ideally
>>living in a data center somewhere so we can automate builds,
>>rather than
>>relying on my laptop and Jim's Windows box which seems to build
>>intermittently.
>>
>>
>
>I might be able to help out there.
>
Excellent.
>What's required to be part of the
>build farm?
>
>
>
>
Short answer:
. your box will need to be able to contact http://www.pgbuildfarm.org
either directly or via proxy, and it wiull need access to a CVS repo,
either the one at postgresql.org or a mirror (you can set up your own
mirror using CSVup on a linux or FBSD box).
. have a working postgresql build environment for your platform (for
Windows this means MSys/MinGW with the libz and libintl stuff, and
ideally native Python and Tcl).
. Windows only: you will need a native perl installed as well as the one
in the MSys DTK. The one from ActiveState works fine.
. download and unpack the latest release of client code from
http://pgfoundry.org/frs/?group_id=1000040
. read instructions at
http://pgfoundry.org/docman/view.php/1000040/4/PGBuildFarm-HOWTO.txt
. get the software running locally using flags --force--nostatus --nosend
. register your machine at http://www.pgbuildfarm.org/register.html
. when you receive credentials, put them in the config file, and
schedule regular builds (without those flags) for the branches you want
to support. (For Windows that should be HEAD and optionally REL8_0_STABLE).
Feel free to ask me questions if anything isn't clear.
There's a short description of how it works at
http://www.onlamp.com/pub/a/onlamp/2005/02/24/pg_buildfarm.html
cheers
andrew