Message-ID: <cccf9ab9-5cc2-c59f-f9db-0befddceb2e2@dunslane.net>
Date: Tue, 10 Jan 2023 10:17:58 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: Announcing Release 15 of the PostgreSQL Buildfarm client
Content-Language: en-US
From: Andrew Dunstan <andrew@dunslane.net>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <c435c473-af47-a213-4130-46a93612dfab@dunslane.net>
In-Reply-To: <c435c473-af47-a213-4130-46a93612dfab@dunslane.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/cccf9ab9-5cc2-c59f-f9db-0befddceb2e2%40dunslane.net>
Precedence: bulk


On 2022-12-31 Sa 10:02, Andrew Dunstan wrote:
> Changes
>
>
>   * 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.


Occasionally things go wrong. It turns out this code was a bit too eager
and ignored the force_every settings in the config file.

There's a hot fix at
<https://github.com/PGBuildFarm/client-code/commit/c9693f86d9bd07b470bb2a106055b5801cd613ec>
and I will push out a new release shortly.


cheers


andrew

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