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: Nazir Bilal Yavuz <byavuz81@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, 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-04T19:03:39Z
Lists: pgsql-hackers
Hi,

On 2026-06-04 09:02:13 -0700, Jacob Champion wrote:
> On Thu, Jun 4, 2026 at 9:00 AM Andres Freund <andres@anarazel.de> wrote:
> > > On the CPAN front, my first attempt tried to do too much, so I'm
> > > testing a solution that just caches the CPAN sources directory. Should
> > > have something shortly.
> >
> > I'm kinda inclined to push what we have and then add the cpan caching on top
> > in subsequent commits?
> 
> Right -- I don't think v1 should wait on CPAN optimization; I just
> wanted to let you know the status.

Pushed it now. Only a tiny change from the last version, Bilal suggested ove
IM to remove the multi-threading argument from robocopy, for performance.

I did futz around with ccache improvements for a bit. I think we're going to
need them, but they're complicated enough to do them separately.


Thanks to Bilal, Jelte and all the review!


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 →
  1. ci: Add GitHub Actions based CI

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