Re: Add PG CI to older PG releases - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Add PG CI to older PG releases
Date
Msg-id 20230811004412.mv7hqpwz2ex44eyd@awork3.anarazel.de
Whole thread Raw
In response to Re: Add PG CI to older PG releases  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2023-08-10 18:09:03 -0400, Tom Lane wrote:
> Nazir Bilal Yavuz <byavuz81@gmail.com> writes:
> > PG CI is added starting from PG 15, adding PG CI to PG 14 and below
> > could be beneficial. So, firstly I tried adding it to the
> > REL_14_STABLE branch. If that makes sense, I will try to add PG CI to
> > other old PG releases.
> 
> I'm not actually sure this is worth spending time on.  We don't
> do new development in three-release-back branches, nor do we have
> so many spare CI cycles that we can routinely run CI testing in
> those branches [1].

I find it much less stressful to backpatch if I can test the patches via CI
first.  I don't think I'm alone in that - Alvaro for example has previously
done this in a more limited fashion (no windows):
https://postgr.es/m/20220928192226.4c6zeenujaoqq4bq%40alvherre.pgsql

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Add PG CI to older PG releases
Next
From: Bruce Momjian
Date:
Subject: Re: [PoC] pg_upgrade: allow to upgrade publisher node