Re: Announcing Release 15 of the PostgreSQL Buildfarm client - Mailing list buildfarm-members

From Andrew Dunstan
Subject Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Date
Msg-id 4c64a49e-fa1a-f1a0-58bf-f432ad327751@dunslane.net
Whole thread Raw
In response to Re: Announcing Release 15 of the PostgreSQL Buildfarm client  (Noah Misch <noah@leadboat.com>)
Responses Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Re: Announcing Release 15 of the PostgreSQL Buildfarm client
List buildfarm-members
On 2022-12-31 Sa 20:55, Noah Misch wrote:
> On Sat, Dec 31, 2022 at 10:02:32AM -0500, Andrew Dunstan wrote:
>>   * check if a branch is up to date before trying to run it
>>     This only applies if the |branches_to_build| setting is a keyword
>>     rather than a list of branches. It reduces the number of useless
>>     calls to |git pull| to almost zero.
> This new reliance on buildfarm.postgresql.org/branches_of_interest.json is
> trouble for non-SSL buildfarm animals.
> http://buildfarm.postgresql.org/branches_of_interest.txt has an exemption to
> allow serving over plain http, but the json URL just redirects the client to
> https.  Can the json file get the same exemption-from-redirect that the txt
> file has?


I didn't realize there were animals left other than mine which had this
issue. I asked the admins some weeks ago to fix this (I don't have
privilege to do so), but have not had a response yet. The temporary
workaround is to use a list of named branches, e.g. instead of 'ALL' use
[qw(REL_11_STABLE REL_12_STABLE REL_13_STABLE REL_14_STABLE
REL_15_STABLE HEAD)]


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




buildfarm-members by date:

Previous
From: Noah Misch
Date:
Subject: Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Next
From: Andrew Dunstan
Date:
Subject: Re: Announcing Release 15 of the PostgreSQL Buildfarm client