drone-cli tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 82.0 of 100

all runs of drone-clicontinuous-deliverycontinuous-integrationpipelines

Session recording

Loading recording...

Download the original recording · fingerprint 0f76e4c6f8081bbd...

What the test found

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.

No third-party credentials needed; a schema-correct mock Drone server (auth GET /api/user, /api/user/repos, /api/repos/{owner}/{repo}/builds, POST /sign) was stood up locally and the real CLI was exercised against it. `drone exec` could not run actual pipelines because Docker is unavailable.

Argusic installed drone-cli in 7 minutes and launched it; verification reached Verified with mock services. 2 of 4 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of drone-cli

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion