Re: Updating IPC::Run in CI? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Updating IPC::Run in CI?
Date
Msg-id 57a66nr4wmt6fpvya2guk2vcvx75myi5cpg4poikgalsealjgs@bqk7c3gyp6cz
Whole thread Raw
In response to Re: Updating IPC::Run in CI?  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-hackers
Hi,

On 2025-12-17 09:46:11 -0800, Jacob Champion wrote:
> On Wed, Dec 17, 2025 at 9:24 AM Andres Freund <andres@anarazel.de> wrote:
> > If you promise to not push a thousand times a day, I'll add you as a
> > contributor to the repo so CI automatically runs and therefore builds the
> > images [1]...
> 
> That'd be helpful. What scary power does this entail, though --

Unless you merge the PR, not much, other than having the generated images to
pg-ci-images-dev (which nothing uses in the normal process of things). Only
builds in the "main" branch are used for pg-ci-images, the repo that postgres'
.cirrus.yml references.


> > [1] They are built in a separate image repo. To use them, GCP_PROJECT in
> > .cirrus.yml needs to be changed to pg-ci-images-dev.
> 
> -- like, if I forget to do that, does it obliterate our prod images?

No, the change you would need to make is to postgresql's .cirrus.yml to *use*
the generated images, since PR builds are not published to pg-ci-images.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Updating IPC::Run in CI?
Next
From: Matthias van de Meent
Date:
Subject: Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements