jenkins-library
Jenkins shared library for Continuous Delivery pipelines.
Runssource: GitHubhomepageGoApache-2.0commit 7cea829d845a
Go, Apache-2.0 licensed. The project labels itself: ci cd, cli, golang, jenkins and open source.
jenkins-library runs. An Argusic agent installed it in 2.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Go 1.27.4 installed from tarball at /tmp/go; piper binary built at /tmp/piper (189 MB); all 2394 unit tests pass with 0 failures across 16 test packages; the binary runs and displays help with ~160 available commands.
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 95 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.
- Install time
- 3 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go build -o /tmp/piper . exited 0; go test -count=1 ./... ran 2394 tests, 0 failures; /tmp/piper --help printed 160 lines of command help; /tmp/piper version showed piper version string
- Model tokens used
- 93,046
- Exact commit tested
- 7cea829d845a
- 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.
root = tree.getroot()
total = sum(int(ts.attrib.get('tests', 0)) for ts in root)
print(f'Total tests in XML: {total}')
\"" in /work/repo
succeeded in 0ms:
Total tests in XML: 2394
2394 tests, 0 failures, 0 errors in test reports. The XML `errors="7"` on the root element is from …
Now let me summarize my findings:
tokens used
93,046
2394 tests, 0 failures, 0 errors in test reports. The XML `errors="7"` on the root element is from …
Now let me summarize my findings: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.
- Nothing broke on the way: zero errors between clone and running.
- 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 2.5 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
Of the 8 ci-cd projects Argusic has installed and timed, jenkins-library was the 6th fastest to reach a running state, and 6 of 8 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.
- A quick evaluation: it was running 2.5 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jenkins-library)Questions
- Does jenkins-library run?
- Yes. jenkins-library runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test jenkins-library?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7cea829d845a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test jenkins-library?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does jenkins-library take to install?
- 2.5 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 jenkins-library need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jenkins-library?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does jenkins-library compare with the alternatives?
- Of the 8 ci-cd projects Argusic has installed and timed, jenkins-library was the 6th fastest to reach a running state, and 6 of 8 reached one at all.
- Where is the evidence for jenkins-library?
- 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.