Jenkins Offloads Controller Disk Bloat by Backing Artifacts with OCI Registries via ORAS

The Jenkins project has highlighted the ORAS Artifact Manager Plugin as its featured tool, establishing a native bridge between Jenkins build lifecycles and Open Container Initiative (OCI) registries. Authored using the CNCF ORAS Java SDK and API plugin, the tool offloads build artifacts and pipeline stashes to any OCI-compliant distribution system—including Harbor, Zot, Docker Registry, and GitHub Packages. Each Jenkins job maps to an OCI repository where builds create a root artifact anchored to the build number, with individual archived files pushed as single-layer OCI manifests linked via the OCI 1.1 subject field. For platform engineers and Jenkins administrators managing enterprise-scale workloads, controller storage exhaustion is one of the most persistent operational pain points. Historically, archived files and transient pipeline stashes accumulated on local controller disks or required complex external storage plugins that were tightly coupled to specific cloud providers. By abstracting artifact and stash persistence to the OCI standard, Jenkins decouples state from controller storage while preserving the familiar artifact browsing experience on the UI. The use of the OCI 1.1 referrers API also allows instant build artifact discovery without relying on fragile custom indexing mechanisms. This development fits into a broader cloud-native trend of standardizing all build outputs onto OCI distribution specifications. Container registries are no longer mere image repositories; modern supply chain tools increasingly use them to house Helm charts, software bills of materials (SBOMs), Cosign signatures, and binary packages. Bringing Jenkins artifact management into this ecosystem closes the divide between traditional CI automation and modern container workflows, enabling uniform retention rules, role-based access control, and unified vulnerability scanning across both application images and intermediate build outputs. In practice, teams adopting the plugin can run leaner, more ephemeral Jenkins controllers in containerized environments like Kubernetes without managing persistent volume bloat for archived artifacts. Platform operators should evaluate registry bandwidth and authentication models to handle high-frequency stash operations across distributed agents. Teams looking to implement this should ensure their target container registry fully supports the OCI 1.1 specification to take complete advantage of the referrers API and annotation metadata.