Re: Heads Up: cirrus-ci is shutting down June 1st - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Heads Up: cirrus-ci is shutting down June 1st
Date
Msg-id ikcoctfuuh7a5blc5idaaxkkkqcfm4lig7gqmdiste3xkn6jfs@roqxunci4tb2
Whole thread
In response to Re: Heads Up: cirrus-ci is shutting down June 1st  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-hackers
Hi,

On 2026-06-15 16:20:02 -0700, Jacob Champion 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?)

It works because the pre-existing installation is left in-place, so the few
includes reaching the "wrong" directory are harmless.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ci: namespace ccache by PostgreSQL major version
Next
From: Ayush Tiwari
Date:
Subject: Re: Caching a partition index's parent OID in the relcache?