You may have heard the most recent announcement from the Jenkins commercial company, CloudBees: They have acquired the Application Release Orchestration (ARO) vendor Electric Cloud in an effort to provide some (but not all) Continuous Delivery functionality. This is great news, and we’d like to congratulate our colleagues at CloudBees and Electric Cloud. (You may be surprised to hear me say that, since we are, of course, a competitor of Electric Cloud.)
The acquisition is certainly important industry news, but it’s even more than that—it’s a proof point. One that ends—once and for all—the long-standing, number one question about Jenkins:
Can Jenkins and/or CloudBees be used for enterprise-scale, end-to-end Continuous Delivery?
The answer is NO.
The answer is no despite the fact that, until recently, both the CloudBees website and CloudBees general market messaging insisted that they “are building the world’s first end-to-end continuous software delivery system.”
Jenkins is a fabulous CI tool, but for end-to-end Continuous Delivery it’s not enough. End-to-end CD requires a true, built-from-the-ground-up DevOps platform that can scale across the needs of different enterprise teams and different technology stacks, and that supports migration to the cloud and container platforms. Such a solution must be usable for developers and technical users, and for the non-technical users, who play a key role in application build, release management, and deployment.
It’s good to see the leaders of the Jenkins project acknowledge that Jenkins is a CI tool and not a CD platform.
We invite the Jenkins community to take a look at the XebiaLabs DevOps Platform, which provides the end-to-end DevOps functionality required by the largest and most complex companies across the globe—and, of course, integrates with Jenkins as well as hundreds of other popular DevOps tools out-of-the box.
Give your technical and business teams intelligence, automation, and control. Start your free 30 day trial of the XebiaLabs DevOps Platform today!