Re: Announcing Release 15 of the PostgreSQL Buildfarm client

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: buildfarm-members(at)lists(dot)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Date: 2023-01-01 01:55:51
Message-ID: 20230101015551.GA1597914@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

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?

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2023-01-01 02:11:04 Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Previous Message Andrew Dunstan 2022-12-31 15:02:32 Announcing Release 15 of the PostgreSQL Buildfarm client

Browse pgsql-hackers by date

  From Date Subject
Next Message Vik Fearing 2023-01-01 02:05:14 Re: Infinite Interval
Previous Message Peter Geoghegan 2023-01-01 00:53:29 Fixing a couple of buglets in how VACUUM sets visibility map bits