Re: Heads Up: cirrus-ci is shutting down June 1st
Nazir Bilal Yavuz <byavuz81@gmail.com>
From: Nazir Bilal Yavuz <byavuz81@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>,
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-17T11:21:32Z
Lists: pgsql-hackers
Hi, On Tue, 16 Jun 2026 at 02:20, Jacob Champion <jacob.champion@enterprisedb.com> wrote: > > On Fri, Jun 12, 2026 at 2:54 PM Andres Freund <andres@anarazel.de> wrote: > > I did try creating an archive of an install, but that ends up with a good bit > > of additional complexity, because the installations aren't relocatable (there > > are header paths that are patched during install, apparently). And where the > > install should be depends on the runner type, larger runners don't have D:, > > but slower runners require using D:. I think Bilal hacked further on my > > experiments around this, but I don't quite know where that stands. It's > > certainly not a trivial change. > > Huh. (How does the current robocopy relocation work, then?) The current robocopy step happens before the packages are installed. Therefore, it seems there is nothing problematic with the default MSYS installation, but rather that packages installed later cause the problem. -- 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