Date: Sat, 31 Dec 2022 17:55:51 -0800
From: Noah Misch <noah@leadboat.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: buildfarm-members@lists.postgresql.org,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Message-ID: <20230101015551.GA1597914@rfd.leadboat.com>
References: <c435c473-af47-a213-4130-46a93612dfab@dunslane.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c435c473-af47-a213-4130-46a93612dfab@dunslane.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: 
 <https://www.postgresql.org/message-id/20230101015551.GA1597914%40rfd.leadboat.com>
Precedence: bulk

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?