Re: Heads Up: cirrus-ci is shutting down June 1st
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Peter Eisentraut <peter@eisentraut.org>, Nazir Bilal Yavuz <byavuz81@gmail.com>,
Jacob Champion <jacob.champion@enterprisedb.com>, Thomas Munro <thomas.munro@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>, Zsolt Parragi <zsolt.parragi@percona.com>
Date: 2026-06-03T15:20:00Z
Lists: 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
ci: Add GitHub Actions based CI
- 9c126063b19a 19 (unreleased) landed
-
ci: Remove support for cirrus-ci based CI
- 68c8a365d4dc 19 (unreleased) landed