Re: Heads Up: cirrus-ci is shutting down June 1st

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Nazir Bilal Yavuz <byavuz81@gmail.com>, Jelte Fennema-Nio <postgres@jeltef.nl>, Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers@postgresql.org, Zsolt Parragi <zsolt.parragi@percona.com>
Date: 2026-06-03T19:56:59Z
Lists: pgsql-hackers
Hi,

On 2026-06-03 11:12:43 -0700, Jacob Champion wrote:
> On Tue, Jun 2, 2026 at 11:43 AM Andres Freund <andres@anarazel.de> wrote:
> > On 2026-06-02 20:08:17 +0200, Peter Eisentraut wrote:
> > > +  # FIXME: Should we also run on PRs?
> > >
> > > I don't know why we would, since we don't use them.
> >
> > 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...
>
> I guess I'll pipe up again to mention that we have a lot of downstream
> forks.

I'm not entirely unconcerned, but I think requiring explicit per-repo
configuration in a postgres specific way will cause more harm long term, than
some folks having to figure out how to disable the workflow.

FWIW, I did add a section about disabling the workflow to src/tools/ci/README.


> Are we certain that GitHub isn't going to opt them all into
> test-every-stable-commit-and-PR on their next sync?

It'd not test every stable commit, just the ones separately pushed, no?

Greetings,

Andres Freund



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. ci: Add GitHub Actions based CI

  2. ci: Remove support for cirrus-ci based CI