From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Draft release notes complete |
Date: | 2012-09-05 23:06:14 |
Message-ID: | 5047DAE6.4040408@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/05/2012 06:13 PM, Peter Eisentraut wrote:
> On 8/29/12 11:52 PM, Andrew Dunstan wrote:
>>>> Why does this need to be tied into the build farm? Someone can surely
>>> set up a script that just runs the docs build at every check-in, like it
>>> used to work. What's being proposed now just sounds like a lot of
>>> complication for little or no actual gain -- net loss in fact.
>> It doesn't just build the docs. It makes the dist snapshots too.
> Thus making the turnaround time on a docs build even slower ... ?
A complete run of this process takes less than 15 minutes. And as I have
pointed out elsewhere that could be reduced substantially by skipping
certain steps. It's as simple as changing the command line in the
crontab entry.
The only reason there is a significant delay is that the administrators
have chosen not to run the process more than once every 4 hours. That's
a choice not dictated by the process they are using, but by other
considerations concerning the machine it's being run on. Since I am not
one of the admins and don't really want to take responsibility for it I
am not going to second guess them. On the very rare occasions when I
absolutely have to have the totally up to date docs I build them myself
- it takes about 60 seconds on my modest hardware.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-09-05 23:24:08 | Re: Draft release notes complete |
Previous Message | Gurjeet Singh | 2012-09-05 22:57:53 | Report proper GUC parameter names in error messages |