From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | buildfarm-members(at)lists(dot)postgresql(dot)org, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Announcing Release 14 of the PostgreSQL Buildfarm client |
Date: | 2022-02-06 14:01:24 |
Message-ID: | 4b19d29e-e158-534d-5dbd-57a4e34fdc23@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-06-30 15:33:18 | PG v15 branch has been made |
Previous Message | Mikael Kjellström | 2022-01-21 22:42:49 | Re: Buildfarm update to Python 3 needed |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-02-06 15:45:25 | Re: pg_walinspect - a new extension to get raw WAL data and WAL stats |
Previous Message | Andrew Dunstan | 2022-02-06 13:32:59 | Re: pg_upgrade should truncate/remove its logs before running |