drone-cli

Command Line Tools for Drone CI

Runs with mockssource: GitHubhomepageGoApache-2.0commit 3c6e2027200d

Go, Apache-2.0 licensed. The project labels itself: continuous delivery, continuous integration and pipelines.

drone-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.

The drone CLI builds and installs with Go 1.23.8, its test suite passes (2 tests PASS, no failures), and the binary successfully runs version, lint, starlark/jsonnet code generation, and info, repo ls, build ls and sign commands against a local mock Drone server.

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 82 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
82 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
1
last tested
stars
436
forks
186
open issues
29
watchers
14
size
16 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 drone-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.

  • mock server process was killed between exec commands (only shell children of the exec session persisted)4 minutes
  • curl failed to write go.tar.gz to /work (root-owned dir, no write permission for runner)2 minutes
  • `drone exec` requires the Docker daemon (docker binary not present, no root to install)1 minute
  • `drone verify` subcommand does not exist in this version of the CLI1 minute
Install time
7 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
4 hit, 2 fixed with no human help
How the result was proved
GOPATH/bin/drone --version printed 'drone version 0.1.0'; `go test -count=1 -v ./drone/internal/... ./drone/jsonnet/...` exited 0 with 2/2 PASS and `go test ./...` exited 0; against the mock, `drone info` printed 'User: octocat', `drone repo ls` printed 'octocat/hello-world octocat/drone-cli', `drone build ls octocat/hello-world` printed 'Build #42 Status: success', and `drone sign --save` appended a signature resource
Model tokens used
255,375
Exact commit tested
3c6e2027200d
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

=== RUN   TestConvert
=== RUN   TestConvert/Stream_+_Format
=== RUN   TestConvert/Jsonnet_Path
--- PASS: TestConvert (0.00s)
PASS
ok    github.com/drone/drone-cli/drone/jsonnet  0.004s
2
0
All checks are done. I verified the full install path (`go install ./...`), the test suite, real CL…
tokens used
255,375
All checks are done. I verified the full install path (`go install ./...`), the test suite, real CL…

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

  • Installed in 7 minutes.
  • Licensed Apache-2.0, as reported by its host.

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.
  • Hit 4 errors during setup, 2 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs with mocks82.000.05

Topics (from GitHub)

continuous-deliverycontinuous-integrationpipelines

Embed the badge

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

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

Questions

Does drone-cli run?
drone-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test drone-cli?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3c6e2027200d. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test drone-cli?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does drone-cli take to install?
7 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 drone-cli need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing drone-cli?
4 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.
Where is the evidence for drone-cli?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion