Re: Is anybody using .cirrus.yml?

From: Patrick Steinhardt <ps@pks.im>
Date: Nov 4, 2026, 12:25 UTC
Message-ID: <auskIPBRorDxDj6N@pks.im>
In-Reply-To: <20261104095752.2rs5_%taahol@utu.fi>

On Wed, Nov 04, 2026 at 11:57:52AM +0200, Tuomas Ahola wrote:

Show 13 quoted lines

> Carlo Arenas <carenas@gmail.com> wrote:
> 
> > On Mon, Nov 2, 2026 at 11:41 PM Patrick Steinhardt <ps@pks.im> wrote:
> > 
> > > Anyway, if nobody runs it anymore we should remove it. But let's wait a
> > > few days for Carlo to answer in case he still does have a usecase for
> > > it before we send a patch to drop it.
> > 
> > Thanks, but there is no reason to keep that file around AFAIK.
> > 
> > Carlo
> 
> Thanks both.  May I have your acks please?

I think it would help if you sent this as a separate patch. Otherwise, this patch here is going to be very hard to discover for anybody who isn't reading this thread.

> -----8<-----
> Subject: [PATCH] CI: delete defunct Cirrus CI configuration

s/CI:/ci:/

Show 6 quoted lines

> Since b5a9d7afcd (CI: add FreeBSD CI support via Cirrus-CI,
> 2019-12-20), .cirrus.yml has powered Git's VM-based FreeBSD CI.
> 
> However, with the shutdown of Cirrus CI on 2026-06-01, there
> don't seem to be any drop-in solutions available to support our
> usecase---while there exist tools in general to run Cirrus pipelines

The three dashes are a bit funny, but okay.

Show 5 quoted lines

> locally, managing FreeBSD VMs doesn't appear to be covered.
> 
> That renders .cirrus.yml completely nonfunctional.  Delete it.
> 
> Signed-off-by: Tuomas Ahola <taahol@utu.fi>

Other than that this looks good to me. As said though, might make sense to send this via a separate thread so that it becomes disocverable.

Patrick