jenkins

What is Jenkins?

The jenkins image runs the Jenkins automation server — a long-standing, plugin-driven CI/CD tool used to orchestrate builds, tests, and deployments. The official `jenkins/jenkins` image packages the Jenkins LTS release with sensible defaults and a writable `/var/jenkins_home`. Jenkins deploys as a controller plus one or more agents, with pipelines defined in `Jenkinsfile` and a deep plugin ecosystem.

What is Echo's Jenkins image?

Echo's jenkins image is a hardened build of Jenkins LTS on a hardened JDK and base. Echo images are designed to be a drop-in replacement: change the FROM line in your Dockerfile and CVEs go to zero without breaking your app. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For the controller pod, the default variant is the right choice (you'll want a shell to debug plugins); the distroless variant is suitable for ephemeral build agents.

 What is the difference between Echo's Jenkins image and the public Jenkins image?

Public jenkins images bring an OS toolchain that is convenient for plugins but contributes CVEs your security team has to track on a long-lived controller. Echo's build trims the base while keeping plugin loading and Groovy execution intact, dropping the controller's CVE count to zero. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

 FAQ

 Can I replace my jenkins image with Echo's jenkins image?

Yes. Echo's jenkins image is a drop-in replacement. Update the FROM line in your Dockerfile (or the image reference in your manifests) and your application keeps working — the CVEs disappear, the behavior doesn't.

 Is Echo's jenkins image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated.

 What is Echo's vulnerability management SLA on the jenkins image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version.

 Is Echo's jenkins image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells.

 How does Echo achieve such a drastic CVE reduction in jenkins?

Echo jenkins is built from source with only the absolute essentials needed to run the workload, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the version that works for you without forcing a functional change for the sake of security.

 Will Echo's jenkins image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting.

‍