Jenkins: automation server for builds, tests and deployments. Signed; SBOM and SLSA v1 provenance.
8.5K
readystack/jenkins:2.580.2-CE-ubuntu24.04-r3
Source, recipe and records
jenkins-2.580.2): https://github.com/jenkinsci/jenkins/tree/ea3f958268fe87ed86a5d1c2d90c5a99426b97ceA cosign-signed build of github.com/jenkinsci/jenkins jenkins-2.580.2 (MIT; bundled Winstone is LGPL/CDDL, CDDL elected; the 63 bundled plugins are upstream's prebuilt releases, unmodified), built clean-room from official upstream source by ReadyStack.
Who: Development and DevOps teams who automate building, testing and deploying their software.
Why: Jenkins is an open-source automation server. With its plugins it runs the repetitive parts of the development workflow: builds, tests, static code analysis and deployments.
Use case: Each time a developer pushes code, Jenkins checks it out, builds it and runs the test suite, so a bug is caught as soon as it is introduced. When the tests pass on the main branch, the same pipeline deploys the build to a test environment.
About the upstream project, written from its own description: https://github.com/jenkinsci/jenkins · https://www.jenkins.io/
Signature, user and attestations below were measured on the published digest sha256:4915eec7f1729c0dea6ec6fde45eee1ed62cb86c2f975850c6360bf6ac145207 on 2026-11-17.
04daa92344a52dbc) on this release's index digest sha256:4915eec7f1729c0dea6ec6fde45eee1ed62cb86c2f975850c6360bf6ac145207; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/jenkins:2.580.2-CE-ubuntu24.04-r3.jenkins).This image follows the ReadyStack release-tag convention:
The current release is 2.580.2-CE-ubuntu24.04-r3 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement.
Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.
Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html
Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.
# ✓ current release
docker pull readystack/jenkins:2.580.2-CE-ubuntu24.04-r3
# ✗ unsupported (do not pull)
docker pull readystack/jenkins:internal-...
This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/jenkins:2.580.2-CE-ubuntu24.04-r3 (the signature is recorded in the public Sigstore transparency log). Support: [email protected], as set out in the ReadyStack Agreement.
Single container running jenkins.war on its embedded Winstone/Jetty container, with state under JENKINS_HOME. No external database.
Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create jenkins.env with install -m 600 /dev/null jenkins.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.
# First start only: the first start of an empty JENKINS_HOME creates the administrator (JENKINS_ADMIN_USER, default admin) with JENKINS_ADMIN_PASSWORD. Remove this line after setup and recreate the container; the administrator keeps the password.
JENKINS_ADMIN_PASSWORD=YOUR_ADMIN_PASSWORD
docker run -d --name jenkins -p 8080:8080 --env-file ./jenkins.env -v jenkins-home:/var/jenkins_home readystack/jenkins:2.580.2-CE-ubuntu24.04-r3
Sign in at http://localhost:8080 as admin with the password from jenkins.env. Once the first start has created the administrator, remove the JENKINS_ADMIN_PASSWORD line from jenkins.env and recreate the container on the same volume (docker rm -f jenkins, then the docker run command again): the entrypoint needs the variable only while JENKINS_HOME has no security realm, so Jenkins starts, the administrator keeps the password, and the password is no longer in the container's environment.
The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/jenkins. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:bfcf982e66ef1e631b05f3fb978df3589d35e17212e1fb1fbc7e445cf20b1f5a on 2026-11-17.
— ReadyStack · readystack.dev
Content type
Image
Digest
sha256:4915eec7f…
Size
175.7 MB
Last updated
1 day ago
docker pull readystack/jenkins:2.580.2-CE-ubuntu24.04-r3