concourse

Concourse is a container-based automation system written in Go. It's mostly used for CI/CD.

Runssource: GitHubhomepageGoApache-2.0commit d6e25a33812a

Go, Apache-2.0 licensed. The project labels itself: ci, ci cd, concourse, containerd, containers, continuous delivery, continuous integration and elm.

concourse runs. An Argusic agent installed it in 13 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Concourse binary compiles and runs (--help, --version, generate-key all work). 27 Go unit test suites pass (flag, tracing, vars, fly commands/subsystems, worker runtime/spec/integration/network, atc engine/resource/vault/transport, worker baggageclaim volume). Elm frontend dependencies installed; subset of Elm unit tests pass.

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

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
7,939
forks
914
open issues
79
watchers
136
size
156 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 concourse, 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 (1.27.1) not installed in container2 minutes
  • Yarn package manager not available (no corepack, no global npm install)2 minutes
  • PostgreSQL (initdb) not installed - 12 test suites skipped (cmd/concourse, atc/worker/gardenruntime)
  • worker/baggageclaim/volume/driver tests fail (4/9 spec failures) - require overlayfs mount/btrfs kernel features not available in container
  • Full Elm test suite (58 test files) gets killed by OOM (RSS > 100MB on socket communication)
Install time
13 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
go build ./cmd/concourse/ exited 0 producing /tmp/concourse (136 MB ELF); /tmp/concourse --version returned '0.0.0-dev'; /tmp/concourse --help returned listing 6 subcommands; go test -count=1 on 27 packages all reported 'ok'; go test on ./worker/baggageclaim/volume/driver reported 4 failures (overlay/btrfs); elm-test tests/DurationTests.elm passed 4/4
Model tokens used
401,589
Exact commit tested
d6e25a33812a
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.

exec
/bin/sh -lc 'date +%s' in /work/repo
 succeeded in 0ms:
1793899449
exec
/bin/sh -lc 'echo "Total elapsed: about 10 minutes"' in /work/repo
 succeeded in 0ms:
Total elapsed: about 10 minutes
Here's my full report on the Concourse repository:
tokens used
401,589
Here's my full report on the Concourse repository:

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.
  • 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 13 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 ci projects Argusic has installed and timed, concourse was the 5th fastest to reach a running state, and 3 of 5 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.10
Argusic Runner1/3Runs with mocks92.000.44

Topics (from GitHub)

cici-cdconcoursecontainerdcontainerscontinuous-deliverycontinuous-integrationelmgopipelinesrunc

Embed the badge

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

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

Questions

Does concourse run?
Yes. concourse runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test concourse?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d6e25a33812a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test concourse?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does concourse take to install?
13 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 concourse need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing concourse?
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.
How does concourse compare with the alternatives?
Of the 5 ci projects Argusic has installed and timed, concourse was the 5th fastest to reach a running state, and 3 of 5 reached one at all.
Where is the evidence for concourse?
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