Re: Heads Up: cirrus-ci is shutting down June 1st - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id hwvjhblr4ww4sovkbocdl7tjpvtpxqhdxvrsrwbkdf4zfbtcv2@35k2ncivj36g
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
Hi,

On 2026-06-02 21:06:39 +0200, Jelte Fennema-Nio wrote:
> On Tue, Jun 2, 2026, 20:43 Andres Freund <andres@anarazel.de> wrote:
> 
> > From what I can tell the workflow of plenty folks during their own
> > development
> > is to open PRs in their own repo.  I don't really see a downside to also
> > running on PRs, so I'm inclined to do so. Won't hurt us...
> >
> 
> Generally you should do one or the other. Otherwise all jobs will be run
> twice when you push to a branch that is linked to a PR. So I'd say, only do
> push

I think that maybe could be addressed with a bit of conditional logic, by
looking at github.event.pull_request.head.repo or such, and skipping jobs if
it's in the same repo?

But I don't want to experiment with that before adding back basic CI, so I'll
leave this for later.


I also would like to allow to start CI via workflow_call, with inputs for the
container tag to be used, so we could run PG CI after building the containers
used by CI, before tagging them as latest. But that's also seems stuff for
later.

Greetings,

Andres



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Next
From: Jim Jones
Date:
Subject: Re: BUG with accessing to temporary tables of other sessions still exists