cirrus-cli

CLI for executing Cirrus tasks locally and in any CI

Runs with mockssource: GitHubGoMITcommit 1769788a20dc

Go, MIT licensed. The project labels itself: ci cd, containers, devops and golang.

cirrus-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Cirrus CLI builds successfully with Go 1.27.3, all 55 test packages pass, and the binary produces its version and help output

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.46 (measured)
recorded runs
2
last tested
stars
294
forks
35
open issues
23
watchers
4
size
4 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing cirrus-cli, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Two tests (TestAdditionalInstanceCredentials, TestValidateCloudInstance) fail because grpc.cirrus-ci.com:443 is unreachable10 minutes
  • Go 1.27+ not available in environment2 minutes
Install time
12 minutes
Cold machine to finish
43 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test ./... exited 0, 55 packages passed, /tmp/cirrus --version printed 'cirrus version 0.0.0-20260601171231-1769788a20dc+dirty-unknown'
Model tokens used
1,205,467
Exact commit tested
1769788a20dc
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

All tests passed - no FAIL lines found
All tests pass with zero failures. Let me compile the final report and produce the ARGUSIC_RESULT.
exec
/bin/sh -lc 'export PATH=$HOME/go-toolchain/go/bin:$PATH GOPATH=$HOME/gopath; cd /work/repo && /tmp…
 succeeded in 1208ms:
cirrus version 0.0.0-20260601171231-1769788a20dc+dirty-unknown
ok    github.com/cirruslabs/cirrus-cli/pkg/parser  0.415s
ok    github.com/cirruslabs/cirrus-cli/internal/commands/validate  0.023s
All tests pass. Here's my final report.
tokens used
1,205,467
All tests pass. Here's my final report.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 12 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.

Of the 8 ci-cd projects Argusic has installed and timed, cirrus-cli was the 7th fastest to reach a running state, and 6 of 8 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.46
Argusic Runner1/3Did not run20.000.31

Topics (from GitHub)

ci-cdcontainersdevopsgolang

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/cirrus-cli.svg)](https://argusic.com/subject/cirrus-cli)

Questions

Does cirrus-cli run?
cirrus-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test cirrus-cli?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1769788a20dc. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test cirrus-cli?
The run that produced this verdict cost $0.46: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does cirrus-cli take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does cirrus-cli need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing cirrus-cli?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does cirrus-cli compare with the alternatives?
Of the 8 ci-cd projects Argusic has installed and timed, cirrus-cli was the 7th fastest to reach a running state, and 6 of 8 reached one at all.
Where is the evidence for cirrus-cli?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion