gocd
GoCD - Continuous Delivery server main repository
Runssource: GitHubhomepageJavaApache-2.0commit 9a49867bc654
Java, Apache-2.0 licensed. The project labels itself: cd, ci, ci cd, continuous delivery, continuous delivery server, continuous deployment, continuous integration and continuous testing.
gocd runs. An Argusic agent installed it in 41 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
GoCD builds successfully with full Java compilation (149 Gradle tasks). The server test suite passes 3362 of 3365 tests across 20+ modules, with only SCM-binary-dependent tests (svn, hg, p4, ant) failing due to missing tools in the container environment, and one pre-existing mock test issue.
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 100 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 Java JDK found in container5 minutes
- Gradle toolchain requires JDK 25 but auto-provisioning disabled1 minute
- JRuby initializeRailsGems fails with 'Could not create JVM' due to --sun-misc-unsafe-memory-access=allow flag not supported by JDK 211 minute
- SCM binary tests fail: svn, hg, p4, ant not installed (no root)
- JettyWorkDirValidatorTest.shouldSetJettyHomeAndBasePropertyIfItsNotSet fails - pre-existing test design issue with Mockito mock vs System.setProperty
- Install time
- 41 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- Full project compiles (149 tasks, BUILD SUCCESSFUL). Test suites across 20+ modules executed. Server module: 3362/3365 passed (3 failures: 2 missing svn/ant, 1 pre-existing mock test issue). Passing modules included base (91/91), util (18/18), commandline (62/62), jetty (59/59), db (30/30), config-api (2084/2084), config-server (436/436), spark (177/177), plugin-infra (182/182), agent-launcher (70/70), agent-common (62/62), and 13 API modules (105/105).
- Model tokens used
- 148,289
- Exact commit tested
- 9a49867bc654
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
13 API modules: 105/105 pass server: 3362/3365 pass (3 failures: 2 missing svn/ant, 1 pre-existing test issue) === FAILING (ENVIRONMENT ONLY) === domain: 661/824 pass, 163 fail (missing svn/hg/p4) common: 538/581 pass, 43 fail (missing hg/svn) agent: 96/115 pass, 19 fail (missing svn) exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1790603870 tokens used 148,289
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
- Reached a running state on a clean machine, with the session recorded.
- Installed in 41 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
cdcici-cdcontinuous-deliverycontinuous-delivery-servercontinuous-deploymentcontinuous-integrationcontinuous-testinggocdinfrastructure-as-code
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gocd)Questions
- Does gocd run?
- Yes. gocd runs. Argusic installed and launched it on a clean machine in 41 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test gocd?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9a49867bc654. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test gocd?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gocd take to install?
- 41 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 gocd need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gocd?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for gocd?
- 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.