This article is based on reporting originally published on devops.com, covering announcements made at DevOps World | Jenkins World 2019.
CloudBees Doubles Down on Enterprise Continuous Delivery
At the DevOps World | Jenkins World 2019 conference, CloudBees announced a significant update to its continuous delivery (CD) platform, originally acquired through its purchase of Electric Cloud. The rebranded product, now called CloudBees Flow, represents the company’s continued investment in enterprise-grade application release orchestration (ARO) — and signals an ambition to own the “last mile” of the DevOps pipeline.
CloudBees CEO Sacha Labourey framed the release as a direct response to a persistent gap in enterprise DevOps maturity: while SaaS-native companies have refined their delivery processes over years, most traditional enterprise IT organizations are still defining — let alone standardizing — their end-to-end DevOps practices.
What’s New in CloudBees Flow 9.1
Version 9.1 of CloudBees Flow introduces several capabilities aimed at improving visibility, control, and compliance across complex release pipelines:
- Release inventory visibility: Teams can now view exactly what is being deployed to a given environment at any point during a release, reducing ambiguity in multi-team delivery scenarios.
- Sub-pipeline insights: Deeper observability into all the sub-pipelines that compose an overall release makes it easier to pinpoint bottlenecks or failures in large, orchestrated workflows.
- Granular pipeline execution controls: More fine-grained controls over release pipeline execution allow teams to pause, approve, or roll back specific stages without affecting the entire pipeline.
- Customizable Release Command Center dashboards: Teams can tailor their operational view to surface the metrics and pipeline states most relevant to their release process.
- Data archiving for compliance: New archiving capabilities make it easier for organizations to meet regulatory requirements by retaining auditable records of release activity.
The ARO Platform and the Last Mile of DevOps
Application release orchestration addresses one of the hardest problems in enterprise DevOps: coordinating deployments across multiple teams, environments, and interdependent applications. While continuous integration (CI) tooling has matured considerably — Jenkins being the dominant example — continuous delivery at enterprise scale remains a significantly harder problem to solve.
Common pain points include ensuring the right infrastructure resources are available for a new release, managing environment drift, handling rollback scenarios, and debugging production deployments. CloudBees Flow is positioned to address these challenges by sitting on top of existing CI/CD pipelines and orchestrating the full release process, not just the build and test stages.
A Roadmap Toward Unified Continuous Delivery
Labourey outlined a longer-term goal: unifying CD processes across multiple platforms under a coherent CloudBees umbrella. The platforms in scope include:
- CloudBees Flow (formerly Electric Flow) — enterprise ARO for complex, multi-tier application releases
- Jenkins — the widely adopted CI/CD automation server
- Jenkins X — a Kubernetes-native CI/CD platform optimized for cloud-native and microservices workloads
- Spinnaker — a multi-cloud continuous delivery platform also optimized for microservices on Kubernetes
Each platform addresses a different segment of the delivery landscape, and unifying them under a common framework is a non-trivial engineering and organizational challenge. However, having a portfolio that spans traditional enterprise applications and modern cloud-native services positions CloudBees to serve organizations at varying stages of their DevOps journey.
CloudBees and the Continuous Delivery Foundation
Earlier in 2019, CloudBees became a founding member of the Continuous Delivery Foundation (CDF), a Linux Foundation project dedicated to fostering best practices, open-source tooling, and vendor-neutral standards around continuous delivery. Other founding members included Google, Netflix, and Capital One. Membership in the CDF positions CloudBees as both a commercial vendor and an active contributor to the broader CD ecosystem — a dual role that can help build credibility with enterprise buyers who are evaluating long-term platform bets.
Why Continuous Delivery Remains Hard for Enterprises
Despite years of investment in DevOps tooling, continuous delivery continues to lag behind continuous integration in enterprise adoption. Several structural challenges account for this:
- Organizational complexity: Enterprise releases often involve dozens of teams, each with their own pipelines, approval gates, and deployment targets.
- Environment heterogeneity: Unlike greenfield cloud-native apps, most enterprise applications span on-premises infrastructure, legacy systems, and cloud environments simultaneously.
- Risk tolerance: Production deployments in regulated industries — financial services, healthcare, government — carry compliance and audit requirements that slow down automated release cadences.
- Toolchain fragmentation: Few enterprises use a single CI/CD toolchain; most have accumulated a patchwork of tools across business units and geographies.
These are precisely the problems that ARO platforms like CloudBees Flow are designed to address — not by replacing existing tooling, but by orchestrating across it.
The Broader DevOps Context
The question for most mature enterprises has shifted. It is no longer whether to adopt DevOps, but which processes, platforms, and standards to standardize on across the organization. As software delivery velocity becomes a direct competitive differentiator, the pressure on engineering and platform teams to get this right has increased substantially. Legacy deployment processes — manual approvals, infrequent releases, siloed change management — simply cannot scale to meet the expectations of modern digital businesses.
CloudBees Flow 9.1, and the broader CloudBees portfolio, reflects a bet that enterprises need a commercial platform layer above open-source CI/CD tools to manage the scale, governance, and cross-team coordination demands of enterprise software delivery. Whether that bet pays off depends heavily on how well CloudBees can deliver on its platform unification roadmap.