Message-ID: <4b19d29e-e158-534d-5dbd-57a4e34fdc23@dunslane.net>
Date: Sun, 6 Feb 2022 09:01:24 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Content-Language: en-US
From: Andrew Dunstan <andrew@dunslane.net>
Subject: Announcing Release 14 of the PostgreSQL Buildfarm client
To: buildfarm-members@lists.postgresql.org,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/4b19d29e-e158-534d-5dbd-57a4e34fdc23%40dunslane.net>
Precedence: bulk

Significant changes:

  * don't run TestUpgrade if TAP tests are present in |src/bin/pg_upgrade|
  * Add proposed new location of |pg_upgrade| logs in TestUpgrade module
  * Use an HMAC over the whole content as the signature.
  * Quote |PROVE_FLAGS |in case there are multiple settings
  * tighten failure detection for cross version upgrade
  * be more verbose about git mirror failures
  * Support symlinks on Windows where possible in SCM module
  * Document |rm_worktrees| setting and make |on| the default.
  * Add new branches_to_build keywords |STABLE| and |OLD|

Because of the changes to how pg_upgrade logging works, owners are
strongly urged to upgrade to the new release as soon as possible if they
are running the TestUpgrade module.

The meaning of the branches_to_build keywords are as follows: STABLE
means all the live branches other than master/HEAD, while OLD means
those branches older than STABLE that we are now supporting limited
builds for (currently REL9_2_STABLE through REL9_6_STABLE).

Downloads are available at
<https://github.com/PGBuildFarm/client-code/releases> and
<https://buildfarm.postgresql.org/downloads>


cheers


andrew