Re: Draft release notes complete - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Draft release notes complete
Date
Msg-id CABUevExdU3scS-tp1P3QD3j_cOgDUgYAJJDt2Qoj3AOeg5rL-w@mail.gmail.com
Whole thread Raw
In response to Re: Draft release notes complete  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Draft release notes complete
Re: Draft release notes complete
List pgsql-hackers
<p><br /> On May 10, 2012 5:24 PM, "Bruce Momjian" <<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>>
wrote:<br/> ><br /> > On Thu, May 10, 2012 at 12:49:51PM +0200, Magnus Hagander wrote:<br /> > > On Thu,
May10, 2012 at 12:43 PM, Andrew Dunstan <<a href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>> wrote:<br
/>> > ><br /> > > ><br /> > > > On 05/10/2012 01:29 AM, Tom Lane wrote:<br /> > >
>><br/> > > >> Bruce Momjian<<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>>
 writes:<br/> > > >>><br /> > > >>> The docs finally built 90 minutes after my commit,
andthe URL above is<br /> > > >>> now working.  (Does it always take this long to update?)<br /> >
>>><br /> > > >> I believe the new implementation of that stuff is that the devel docs<br /> >
>>> are built whenever the buildfarm member guaibasaurus runs for HEAD,<br /> > > >> which it
seemsto do on an hourly schedule.  This is definitely not as<br /> > > >> fast-responding as Peter's former
customscript, but I'm not sure if<br /> > > >> it's worth thinking of another way.<br /> > >
>><br/> > > ><br /> > > > I don't see any reason it can't run more frequently, though.
Currentlya run<br /> > > > takes 15 minutes or so. We could reduce that by making it skip some steps,<br />
>> > and get it down to about 10 minutes. It would be perfectly reasonable to run<br /> > > > every 5
minutes(it won't schedule concurrent runs - if the lock file is<br /> > > > held by another run it exits
gracefully).Of course, that's up to Magnus and<br /> > > > Stefan.<br /> > ><br /> > > If we can
makeit do *just* the docs, we can certainly run it a bit<br /> > > more often. But we don't want to make it run
thefull set of checks<br /> > > more or less continously, since the machine is shared with a number of<br /> >
>other tasks...<br /> > ><br /> > > I don't think 5 minutes is anywhere near necessary even for the
docs,<br/> > > but there is a lot of room between 5 minutes and 4 hours, so we can<br /> > > definitely
shortenit.<br /> ><br /> > Do you want me to just setup a build on my machine like we did before;<br /> > 5
minutesis no problem for me.<br /> ><br /> > I use the doc build to show patch submitters what their final work
looks<br/> > like, and anything more than a few minutes delay makes that useless.<br /> ><p>Anything that runs
offthe main git repo would be useless there, since it would never show up prior to commit.<p>If people want the main
docsbuilding more often that's not really a problem other than time - we just need to decouple it from the buildfarm
andrun a separate job for it. It's not rocket science.. <p>/Magnus  

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: "pgstat wait timeout" just got a lot more common on Windows
Next
From: Bruce Momjian
Date:
Subject: Re: Draft release notes complete