Обсуждение: PG documentation build is wedged
According to http://developer.postgresql.org/pgdocs/postgres/buildlog.html the git-tip documentation build hasn't happened since the 19th, and a quick look-around at http://developer.postgresql.org/pgdocs/postgres/index.html confirms that recent docs changes don't seem to be showing there. regards, tom lane
Excerpts from Tom Lane's message of mié nov 23 23:55:22 -0300 2011: > According to > http://developer.postgresql.org/pgdocs/postgres/buildlog.html > the git-tip documentation build hasn't happened since the 19th, > and a quick look-around at > http://developer.postgresql.org/pgdocs/postgres/index.html > confirms that recent docs changes don't seem to be showing there. I think the devel docs are now supposed to be built by bf member guaibasaurus, but the necessary hooks on the buildfarm client to copy them to the webserver aren't there yet. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Thu, Nov 24, 2011 at 04:32, Alvaro Herrera <alvherre@commandprompt.com> wrote: > > Excerpts from Tom Lane's message of mié nov 23 23:55:22 -0300 2011: >> According to >> http://developer.postgresql.org/pgdocs/postgres/buildlog.html >> the git-tip documentation build hasn't happened since the 19th, >> and a quick look-around at >> http://developer.postgresql.org/pgdocs/postgres/index.html >> confirms that recent docs changes don't seem to be showing there. They are most likely broken because the machine that developer.postgresql.org was upgraded without testing, and has broken completely now. It's been expected for a while, but it's now reached the point where the git command doesn't work. This broke the snapshot builds on the same machine. I haven't verified if they're what broke the dev docs, but it's almost certain. > I think the devel docs are now supposed to be built by bf member > guaibasaurus, but the necessary hooks on the buildfarm client to copy > them to the webserver aren't there yet. It's almost there. Based on current plans, we hope to have the developer docs up and running early next week. (Actually, didn't realize they were broken - it's just that their new location is planned to go live next week, which will implicitly fix this problem) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
On 11/24/2011 02:43 AM, Magnus Hagander wrote:
>
>> I think the devel docs are now supposed to be built by bf member
>> guaibasaurus, but the necessary hooks on the buildfarm client to copy
>> them to the webserver aren't there yet.
> It's almost there. Based on current plans, we hope to have the
> developer docs up and running early next week. (Actually, didn't
> realize they were broken - it's just that their new location is
> planned to go live next week, which will implicitly fix this problem)
You need to change the config of this animal to something like:
optional_steps => { build_docs => { branches => [ 'HEAD' ],
min_hours_since => 0 } },
There's no point in not building the docs for HEAD on every build, since
"make dist" in the new module will build them if they're not built
anyway, but in such a way that they're not so readily usable, whereas
this way you can copy them out easily.
cheers
andrew
Excerpts from Andrew Dunstan's message of jue nov 24 14:44:18 -0300 2011:
> You need to change the config of this animal to something like:
>
> optional_steps => { build_docs => { branches => [ 'HEAD' ],
> min_hours_since => 0 } },
>
>
> There's no point in not building the docs for HEAD on every build, since
> "make dist" in the new module will build them if they're not built
> anyway, but in such a way that they're not so readily usable, whereas
> this way you can copy them out easily.
FWIW while updating this config I noticed that we have --with-ldap on
HEAD and 8.2, but not the other branches; and --with-xml only in HEAD
and 8.3 but not the other branches. I assume this is from the stock
config file (snippets below).
It seems to me that the BF stuff should have some operator to specify
"any branch newer than X".
# ldap support is new as of 8.2
if ($branch eq 'HEAD' || $branch ge 'REL8_2')
{
# msvc can set it up separately - see above
push(@{$conf{config_opts}},"--with-ldap")
unless $conf{using_msvc};
}
# libxml/libxslt support as of 8.3
if ($branch eq 'HEAD' || $branch ge 'REL8_3')
{
# msvc can set it up separately - see above
push(@{$conf{config_opts}},"--with-libxml", "--with-libxslt")
unless $conf{using_msvc};
}
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On 11/24/2011 09:16 PM, Alvaro Herrera wrote:
>
> Excerpts from Andrew Dunstan's message of jue nov 24 14:44:18 -0300 2011:
>
>> You need to change the config of this animal to something like:
>>
>> optional_steps => { build_docs => { branches => [ 'HEAD' ],
>> min_hours_since => 0 } },
>>
>>
>> There's no point in not building the docs for HEAD on every build, since
>> "make dist" in the new module will build them if they're not built
>> anyway, but in such a way that they're not so readily usable, whereas
>> this way you can copy them out easily.
>
> FWIW while updating this config I noticed that we have --with-ldap on
> HEAD and 8.2, but not the other branches; and --with-xml only in HEAD
> and 8.3 but not the other branches. I assume this is from the stock
> config file (snippets below).
>
> It seems to me that the BF stuff should have some operator to specify
> "any branch newer than X".
not sure I follow at all...
>
>
> # ldap support is new as of 8.2
> if ($branch eq 'HEAD' || $branch ge 'REL8_2')
this basically means "do only if $branch is exactly HEAD or if $branch
is greater or equals to REL8_2 which is exactly what you are proposing
and what actually makes sense?
Stefan
Excerpts from Stefan Kaltenbrunner's message of jue nov 24 17:45:07 -0300 2011: > > On 11/24/2011 09:16 PM, Alvaro Herrera wrote: > > # ldap support is new as of 8.2 > > if ($branch eq 'HEAD' || $branch ge 'REL8_2') > > this basically means "do only if $branch is exactly HEAD or if $branch > is greater or equals to REL8_2 which is exactly what you are proposing > and what actually makes sense? Uh, I missed that it was a "ge" operator there. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support