jenkins-rest

Java client, built on top of jclouds, for working with Jenkins REST API

Runssource: GitHubJavaApache-2.0commit 75206d967913

Java, Apache-2.0 licensed. The project labels itself: cd, cdcd, ci, client, continuous integration, devops, java and jclouds.

jenkins-rest runs. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

jenkins-rest client library builds and passes all 100 mock tests with Adoptium JDK 11.0.26 on Ubuntu 24.04.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
414
forks
183
open issues
47
watchers
17
size
3 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.

Install time
3 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
./gradlew clean mockTest exited 0, 100 tests passed, 0 failed
Model tokens used
39,068
Exact commit tested
75206d967913
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.

Now let me compile the final report. Here's everything I observed:
**Install**: Downloaded Adoptium Temurin JDK 11.0.26, extracted it, and used the Gradle wrapper (no…
**Build**: `./gradlew clean build -x integTest` succeeded.
**Tests**: `./gradlew clean mockTest` — all **100 mock tests PASSED**, 0 failures. These exercise t…
**No errors encountered** — the build and tests worked on first attempt with no fixes needed.
tokens used
39,068
Now let me compile the final report. Here's everything I observed:
**Install**: Downloaded Adoptium Temurin JDK 11.0.26, extracted it, and used the Gradle wrapper (no…
**Build**: `./gradlew clean build -x integTest` succeeded.
**Tests**: `./gradlew clean mockTest` — all **100 mock tests PASSED**, 0 failures. These exercise t…
**No errors encountered** — the build and tests worked on first attempt with no fixes needed.

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 3 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 cd projects Argusic has installed and timed, jenkins-rest was the 2nd fastest to reach a running state, and 4 of 6 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 3 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

cdcdcdciclientcontinuous-integrationdevopsjavajcloudsjenkinsjenkins-restrestrest-api

Embed the badge

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

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

Questions

Does jenkins-rest run?
Yes. jenkins-rest 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-rest?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 75206d967913. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test jenkins-rest?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jenkins-rest take to install?
3 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-rest need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jenkins-rest?
Nothing did, in the recorded run: zero errors between clone and running.
How does jenkins-rest compare with the alternatives?
Of the 6 cd projects Argusic has installed and timed, jenkins-rest was the 2nd fastest to reach a running state, and 4 of 6 reached one at all.
Where is the evidence for jenkins-rest?
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.

Discussion