Horton
Menu

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

Andres Freund <andres@anarazel.de>

View thread
From: Andres Freund <andres@anarazel.de>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Nazir Bilal Yavuz <byavuz81@gmail.com>, Jacob Champion <jacob.champion@enterprisedb.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-02T18:43:31Z
Lists: pgsql-hackers 
Hi,

On 2026-06-02 20:08:17 +0200, Peter Eisentraut wrote:
> On 01.06.26 23:57, Andres Freund wrote:
> > Attached is an large incremental patch onto Bilal's version:
> 
> This looks good to me.

Cool.


> (I suppose the 0005 patch was just for testing.

Correct. Things just take too long to iterate otherwise.


> The 0004 patch looks ok but
> could use some explanation in both the commit message and the code.)

It's also not really for commit at this point. I think we should do it, but it
to help more locally than on CI.


> +  # 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...

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