| From: | andrewd(at)pgfoundry(dot)org (User Andrewd) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgbuildfarm - client-code: Provide a new base_port config parameter, |
| Date: | 2010-05-15 23:03:38 |
| Message-ID: | 20100515230338.12C7E10715CD@pgfoundry.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Provide a new base_port config parameter, that does away with the need
to specify a port for each branch. That means the config file doesn't
need to change with each release any more.
Abstract the SCM operations into an SCM class. Implement two subclasses,
one for CVS and one for Git. Supporting a new SCM if we ever wanted to would
now just be a matter of implementing a new subclass and configuring it in
the SCM factory method.
Modified Files:
--------------
client-code:
build-farm.conf (r1.28 -> r1.29)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/build-farm.conf?r1=1.28&r2=1.29)
run_build.pl (r1.106 -> r1.107)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl?r1=1.106&r2=1.107)
Added Files:
-----------
client-code/PGBuild:
SCM.pm (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/PGBuild/SCM.pm?rev=1.1&content-type=text/x-cvsweb-markup)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Andrewd | 2010-05-15 23:40:57 | pgbuildfarm - client-code: strict-ize new code |
| Previous Message | Tom Lane | 2010-05-15 21:41:16 | pgsql: Ensure that pg_restore -l will output DATABASE entries whether or |