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 4 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 CDS binaries (engine, worker, cdsctl) compile and run; 24 Go test packages pass including DB-dependent gorpmapper, cache, websocket, cdn/storage, and all SDK, CLI, worker, and hatchery packages. The api, cdn, hooks, repositories, vcs packages need external PostgreSQL database with migrations and/or VCS credentials which were not configured for end-to-end operation.
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No PostgreSQL available2 minutes
- No Go toolchain in container1 minute
- No Redis available1 minute
- SQL migrations failed on PG 9.3 (no jsonb type)1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go test -tags=skipkeychaintests -count=1 -timeout 120s ./engine/gorpmapper/... returned PASS; go test ./sdk/... returned all ok; go test ./engine/cache/... returned ok; /work/repo/dist/cds-engine version printed 'CDS version:snapshot os:linux...'
- Model tokens used
- 200,926
- 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.
tokens used 200,926 All tests pass with PostgreSQL 16 and Redis standing up. Here's the final summary: **Build & launch** — Go toolchain installed manually, all three binaries (`cds-engine`, `cds-worker… **Test results** — Every package that doesn't require external VCS credentials or a full CDS cluste… - SDK: all 16 packages pass (including `vcs/git` at 98s) - CLI: 2 packages pass - Worker: 3 packages pass - Hatchery: 5 packages pass - Engine: `gorpmapper`, `cache`, `websocket`, `cdn/storage`, `elasticsearch`, `api/keys`, `api/down… - `cdn/storage` core tests (`TestLoadAllItemIDUnknownByUnit`, `TestDeduplicationCrossType`, `TestRu… **Infrastructure** — PostgreSQL 16.14 stood up from embedded JAR binary; Redis 7.4.1 compiled from …
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.
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 4 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 automation projects Argusic has installed and timed, cds was the 4th fastest to reach a running state, and 3 of 4 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.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.
[](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 4 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. One attempt is 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.24: 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?
- 4 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 4 automation projects Argusic has installed and timed, cds was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for cds?
- 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.