cds

Enterprise-Grade Continuous Delivery & DevOps Automation Open Source Platform

Runs with mockssource: GitHubhomepageGoBSD-3-Clausecommit efa68e88c86a

Go, BSD-3-Clause licensed. The project labels itself: automation, continuous delivery, continuous deployment, continuous integration, devops, devops workflow, golang and hacktoberfest.

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

All three Go binaries (cds-engine, cds-worker, cdsctl) build and print correct version metadata. All 33 standalone Go test packages pass. The Angular UI builds to production. The kubernetes contrib plugin build failure is fixed.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.12 (measured)
recorded runs
2
last tested
stars
4,848
forks
459
open issues
168
watchers
80
size
227 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 cds, 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.

  • Go compiler not found in container3 minutes
  • Angular UI requires Node.js >=20.19, system has v18.19.13 minutes
  • Kubernetes plugin build failure: non-constant format string in call to fail()2 minutes
  • Makefile build_all_engine targets cross-compile for 8 OS/arch combos, taking forever1 minute
Install time
30 minutes
Cold machine to finish
36 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go test -tags skipkeychaintests ./sdk/... ./cli/... ./tools/... ./engine/hatchery/... ./engine/worker/... ./contrib/grpcplugins/... 33/33 packages passed, 0 failures. Binary smoke tests: cds-engine-linux-amd64 version printed CDS cds-engine version:snapshot, cds-worker-linux-amd64 version printed CDS cds-worker version:snapshot, cdsctl-linux-amd64 version printed version: snapshot. Angular UI build: npm run build:prod completed in 63s, output at ui/dist/browser/index.html (27932 bytes).
Model tokens used
326,288
Exact commit tested
efa68e88c86a
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.

  git_hash: efa68e88c86a1dc90f9b0fe4f941ffe6775e2368
  build_time: 11/08/26-01:30:48
  keychain: true
exec
/bin/sh -lc 'echo "Total time check:" && date -u +%s' in /work/repo
 succeeded in 0ms:
Total time check:
1794102730
Here's my complete report.
tokens used
326,288
Here's my complete 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 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed BSD-3-Clause, 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 30 minutes to install, slower than the median of the 37 comparable projects Argusic has measured.

Of the 38 automation projects Argusic has installed and timed, cds was the 37th fastest to reach a running state, and 25 of 38 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.12
Argusic Runner1/3Runs with mocks92.000.24

Topics (from GitHub)

automationcontinuous-deliverycontinuous-deploymentcontinuous-integrationdevopsdevops-workflowgolanghacktoberfest

Embed the badge

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

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

Questions

Does cds run?
cds runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 30 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test cds?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit efa68e88c86a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test cds?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does cds take to install?
30 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 cds need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing cds?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does cds compare with the alternatives?
Of the 38 automation projects Argusic has installed and timed, cds was the 37th fastest to reach a running state, and 25 of 38 reached one at all.
Where is the evidence for cds?
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