Is anybody using .cirrus.yml?

Is anybody using .cirrus.yml?

[Tuomas Ahola]

It seems that Cirrus-CI has sort of passed away[1], but are there some other
tools and services available that could ingest our .cirrus.yml?  Or is that
file just gathering dust?

Links:
  1. https://cirruslabs.org/

--Tuomas

Re: Is anybody using .cirrus.yml?

[Patrick Steinhardt]

On Mon, Nov 02, 2026 at 10:41:51PM +0200, Tuomas Ahola wrote:
> It seems that Cirrus-CI has sort of passed away[1], but are there some other
> tools and services available that could ingest our .cirrus.yml?  Or is that
> file just gathering dust?

I didn't even know we still had it, and to the best of my knowledge
nobody uses it nowadays. Which is a bit of a shame because it used to
provide test coverage for FreeBSD, seemingly, and neither GitLab CI nor
GitHub Workflows provide that natively.

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.

Patrick

Re: Is anybody using .cirrus.yml?

[Carlo Arenas]

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

Re: Is anybody using .cirrus.yml?

[Tuomas Ahola]

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?

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

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
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>
---
 .cirrus.yml | 24 ------------------------
 1 file changed, 24 deletions(-)
 delete mode 100644 .cirrus.yml

diff --git a/.cirrus.yml b/.cirrus.yml
deleted file mode 100644
index fef04a3840..0000000000
--- a/.cirrus.yml
+++ /dev/null
@@ -1,24 +0,0 @@
-env:
-  CIRRUS_CLONE_DEPTH: 1
-
-freebsd_task:
-  env:
-    GIT_PROVE_OPTS: "--timer --jobs 10"
-    GIT_TEST_OPTS: "--no-chain-lint --no-bin-wrappers"
-    GIT_SKIP_TESTS: t7815.12
-    MAKEFLAGS: -j4
-    DEFAULT_TEST_TARGET: prove
-    DEFAULT_UNIT_TEST_TARGET: unit-tests-prove
-    DEVELOPER: 1
-  freebsd_instance:
-    image_family: freebsd-14-3
-    memory: 2G
-  install_script:
-    pkg install -y gettext gmake perl5
-  create_user_script:
-    - pw useradd git
-    - chown -R git:git .
-  build_script:
-    - su git -c gmake
-  test_script:
-    - su git -c 'gmake test unit-tests'

base-commit: a018953688f1b10bddf91bff8747068f5f4746a4
-- 
ta/delete-cirrus-ci

Re: Is anybody using .cirrus.yml?

[Patrick Steinhardt]

On Wed, Nov 04, 2026 at 11:57:52AM +0200, Tuomas Ahola wrote:
> 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:/

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

> 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

Re: Is anybody using .cirrus.yml?

[Tuomas Ahola]

Patrick Steinhardt <ps@pks.im> wrote:

> On Wed, Nov 04, 2026 at 11:57:52AM +0200, Tuomas Ahola wrote:
> > -----8<-----
> > Subject: [PATCH] CI: delete defunct Cirrus CI configuration
> 
> s/CI:/ci:/
> 

Sure.

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

An ersatz em dash.  Might be a subtle Junioism I've picked up.

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

Thanks, I'll resend.

> Patrick

Re: Is anybody using .cirrus.yml?

[Ben Knoble]

> Le 4 nov. 2026 à 07:28, Patrick Steinhardt <ps@pks.im> a écrit :
> 
> On Wed, Nov 04, 2026 at 11:57:52AM +0200, Tuomas Ahola wrote:
>> 
>> 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.

It’s a typewriter convention for an em-dash, which is difficult
to distinguish from a hyphen or en-dash in fixed-width fonts.

Re: Is anybody using .cirrus.yml?

[Junio C Hamano]

Patrick Steinhardt <ps@pks.im> writes:

> On Wed, Nov 04, 2026 at 11:57:52AM +0200, Tuomas Ahola wrote:
>> 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:/
>
>> 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.
>
>> 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.

Thanks.  Yes, after showing "how about doing it this way?" patch
late in a thread, starting a new and fresh topic with a polished
(hopefully final) version is very much appreciated.  I also should
make it a habit to do so.