| From: | "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | "Andres Freund" <andres(at)anarazel(dot)de>, "Nazir Bilal Yavuz" <byavuz81(at)gmail(dot)com>, "Thomas Munro" <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Heads Up: cirrus-ci is shutting down June 1st |
| Date: | 2026-05-18 21:22:12 |
| Message-ID: | DIM49A100EY1.2YFS2A6WAI3ZJ@jeltef.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 9 Apr 2026 at 22:55, Andres Freund <andres(at)anarazel(dot)de> wrote:
> https://cirruslabs.org/ burries the lede a bit, but it has further down:
> "Cirrus CI will shut down effective Monday, June 1, 2026."
June 1st is getting really close. *In less than two weeks we won't have
a working CI anymore*. Effectively that's probably one week of calendar
dev time that's left, because almost everyone is at PGConf.dev right
now.
So today I decided to take a stab at an initial GitHub Actions yaml
file, as that seemed like the only viable option within that timeline.
Note: Claude Code wrote this file entirely, following extensive
back-and-forth with me after repeatadly getting red builds due to some
differences between Cirrus and Github Actions.
But finally, I managed to get a green build for all systems that we
support on Cirrus CI!
IMPORTANT CONTEXT: I only did a cursory review of the workflow file that
Claude created. So there's probably still a bunch of cleanup to do, but
I at least wanted to share this initial base. I don't know if I'll have
any more time to work on this before June 1st. I have a newborn that's
taking up a lot of my spare time. So, I'd be very happy if someone else
wants to take this patch over and get it to a committable state.
A few things (apart from more extensive review) that I think should be
improved soon (but maybe not before the first commit):
1. io_uring support is disabled. I couldn't get it to work on the GitHub
Actions runners, I think it's disabled in the host kernel. @Andres
2. It's not using pre-built images at the moment, except for the Linux
docker images I think. So it re-downloads a bunch of dependencies for
every build for most OSes. @Bilal or @Andres
3. There's currently no integration with the CFBot or commitfest yet. @Thomas
P.S. This is not an attempt to decide on the proprietary vs self-hosted
opensource discussion. Self hosting might still be the best long-term
solution. I just don't realistically see that happening within two
weeks.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-GitHub-Actions-yaml-file.patch | text/x-patch | 54.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilia Evdokimov | 2026-05-18 22:13:39 | Re: Extended statistics improvement: multi-column MCV missing values |
| Previous Message | Alexander Pyhalov | 2026-05-18 20:06:31 | Re: Function scan FDW pushdown |