Re: Heads Up: cirrus-ci is shutting down June 1st
Nazir Bilal Yavuz <byavuz81@gmail.com>
From: Nazir Bilal Yavuz <byavuz81@gmail.com>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2026-04-10T11:51:24Z
Lists: pgsql-hackers
Hi, On Fri, 10 Apr 2026 at 14:31, Jelte Fennema-Nio <postgres@jeltef.nl> wrote: > > On Thu, 9 Apr 2026 at 22:55, Andres Freund <andres@anarazel.de> wrote: > > I'd be interested in feedback about how high folks value different aspects: > > My thoughts below. I agree with all of Jelte's points except: > > 4) CI tests as many operating systems as possible > > I think we at minimum need linux+macos+windows. Windows is by far the > system that fails most often for me. BSDs would be good, but they > often tend to be fine if osx and linux work. Personally for me I think > on Cirrus The BSDs didn't meet the useful signal to flakiness noise > ratio (i.e. they tended to mostly break randomly for me). I think BSDs are quite capable of catching issues that others can't catch. That has at least been my experience with OpenBSD. However, I agree that OpenBSD and NetBSD tasks are flaky; I think that is mostly because we generate these VM images from scratch (i.e. other operating systems' VM images were already available on GCP). I don't think FreeBSD is flaky. -- Regards, Nazir Bilal Yavuz Microsoft
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