In case you haven't heard, CloudBees,The Jenkins Enterprise Company, is sadly discontinuing Run@cloud, their runtime PaaS offering. The fact is, the whole Enterprise Jenkins part of their business model has grown so quickly that a strategic move had to be made, and according to the September 11th announcement, CloudBees will be focusing their energies exclusively on their Enterprise Jenkins line, and moving away from their runtime PaaS offering.
It's a bit of a surprise for those who have become ardent fast of the RUN@cloud runtime service, but market forces have pushed this maturing start-up into unanticipated directions, and from this point forward, their focus will be exclusively on their Jenkins Enterprise, Jenkins Operations Center and DEV@cloud offerings.
Looking for a Jenkins CI quickstart? These concise and easy to follow Jenkins tutorials will quickly get you on your way towards mastering the popular continuous integration and continuous delivery tool.
Learn Jenkins fast: A continuous integration quickstart
Part 1 -- Introduction to Jenkins tutorial: Download, installation and configuration
Part 2 -- A simple Jenkins build job example
Part 6 -- Compare Maven versus Jenkins
Part 7 -- Test your knowledge with this Jenkins quiz
Part 8 -- DevOps job prep: Tough Jenkins interview questions and answers
Accelerating development and deployment
"Our business has just been driven crazy by this Jenkins phenomenon," said Steven Harris, Senior VP of Products for CloudBees. "Jenkins usage has tripled in the last three years, and it just keeps going and going." And it is this surge in growth that has moved CloudBees away from their runtime PaaS. "What we decided to do was pay attention to this growing ecosystem, focus on Jenkins and the Enterprise Jenkins business. And as a ramification of that, we are going to be retiring Run@Cloud, the run side of our PaaS."
Of course, CloudBees will still be providing hosted Jenkins services, which will come as good news to those who have leveraged their cloud-based offerings for building, testing and staging applications. After all, it was the ability to use their services to accelerate development and do continuous development and deployment that made the CloudBees offering so attractive. "We always believed that the focus on development time was the differentiator for our PaaS," said Harris. "But the generally accepted definition of PaaS means a runtime environment where you deploy your applications. That's the part we are retiring."
So from here on in, CloudBees with be focusing on large-scale, on-premise usage of Jenkins. Furthermore, as part of this push to further grow the Jenkins footprint, CloudBees has recruited the help of Pivotal and the Cloud Foundry platform. CloudBees Enterprise Jenkins (CBJE) will now be delivered as an add on service for Pivotal's Cloud Foundry, meaning more support and greater adoption around the globe.
The fact is, Jenkins has changed the way software projects are developed, staged, tested and delivered. This new direction for CloudBees will ensure that more and more organizations will enjoy the ongoing benefits of continuous integration and continuous delivery in the future.
How have you used cloud based integration to accelerate development? Let us know.
You can follow Cameron McKenzie on Twitter: @potemcam
- Get started with continuous integration and continuous delivery
- Learn how Git, GitHub and distributed version control is impacting source code management
- Get your builds under control with Maven, Gradle and artifact repositories
- Start developing RESTful microservices with Jakarta EE or Spring Boot
- Test your skills with these Git and CI/CD quizzes
- See how you would do on a Jenkins or DevOps job interview