Originally announced by CloudBees. Source: devops.com.
CloudBees has announced the first release of the CloudBees Jenkins X Distribution — a preconfigured, commercially supported package of Jenkins X designed for enterprise teams that need a stable, predictable foundation for their Kubernetes-native CI/CD pipelines. The release comes with CloudBees-backed support plans, curated documentation, and a defined release cadence intended to shield organizations from the pace of change inherent in a fast-moving open-source project.
What Is the CloudBees Jenkins X Distribution?
Jenkins X is an open-source CI/CD solution built for Kubernetes. It automates the creation of pipelines, preview environments, and GitOps-based promotion workflows. Because it evolves rapidly, new features and fixes land frequently — but so do breaking changes and experimental behaviour that may not be suitable for production use in regulated or risk-averse organisations.
The CloudBees Jenkins X Distribution addresses this tension. Rather than tracking the bleeding edge of the OSS project, it selects the most mature and proven components, packages them into a tested and documented bundle, and releases updates on a monthly cadence. CloudBees commits to:
- Validating every release before it ships
- Publishing clear documentation for each supported feature
- Communicating upcoming changes in advance so teams can plan upgrades
- Preventing unannounced breaking changes from reaching users
- Offering commercial support plans for teams that need a vendor to escalate to
The goal is to give enterprises the confidence to commit to Jenkins X as a long-term platform choice, rather than treating it as an experimental tool.
What Is Included — and What Is Not?
The distribution deliberately does not replicate every feature available in the upstream Jenkins X project. It captures the subset of functionality that CloudBees considers ready for production use and documents it thoroughly.
At the time of the initial release, the CloudBees Jenkins X Distribution included support for:
- Google Kubernetes Engine (GKE) — the primary supported Kubernetes platform at launch
- Preview environments — ephemeral environments automatically created for pull requests
Features not yet supported in the first release included:
- Amazon Elastic Kubernetes Service (EKS) — planned for a future release
- DevPods — developer-in-a-pod workflow support, also planned for later releases
CloudBees stated that new features would be added monthly, with each addition going through testing and documentation before inclusion. Teams that need capabilities not yet in the distribution can continue to use the upstream OSS project, which remains fully available and accepts contributions.
How the Distribution Relates to Jenkins X Open Source
CloudBees positioned the distribution as complementary to — not competitive with — the Jenkins X open-source project. The company framed its reasoning around a pattern familiar from other successful open-source ecosystems: a commercially supported downstream distribution lowers the barrier to enterprise adoption, which in turn drives more real-world usage, more bug reports, more contributors, and ultimately a healthier upstream project.
From this perspective, organisations running the CloudBees Jenkins X Distribution are still running Jenkins X workloads. Their operational experience feeds back into the community’s understanding of what patterns work at scale, which strategic directions are worth pursuing, and which rough edges need the most attention. CloudBees described this as a way of growing the Jenkins X ecosystem, not fragmenting it — drawing a parallel to how Jenkins itself has been sustained by community participation over more than a decade.
For teams comfortable tracking the OSS project directly, nothing changes. The upstream Jenkins X project continues to develop at its own pace, with experimental features available as soon as they land. The distribution simply provides an on-ramp for teams that cannot — or do not want to — maintain that level of engagement with a fast-moving open-source project.
Support and Commercial Options
CloudBees offered paid support plans for organisations adopting the distribution. Support contracts provide access to CloudBees engineers when teams encounter issues, as well as SLA-backed response times that the OSS community alone cannot guarantee. This makes the distribution a viable option for organisations with procurement requirements around vendor accountability, security response, or regulated-industry compliance frameworks that mandate supported software.
Summary
The CloudBees Jenkins X Distribution occupies a familiar position in the open-source software landscape: a commercially curated and supported downstream release of a rapidly evolving community project. For DevOps teams evaluating Kubernetes-native CI/CD tooling, it represents a lower-risk path to adopting Jenkins X — one with defined release windows, documented feature sets, and a commercial support safety net. Teams that want the latest innovations should stay close to the upstream OSS project; teams that need stability and accountability have a clear alternative.
Note: This article is based on the original CloudBees announcement from August 2019. Product availability, supported platforms, and commercial terms may have changed significantly since then. Consult current CloudBees documentation for up-to-date information.