CloudBees Turns Jenkins Continuous Integration into a Cloud Service

Mike Vizard
Slide Show

5 New Use Cases for the Public Cloud

Peel back most attempts to embrace more modern approaches of managing IT environments, known euphemistically as DevOps, and you’ll find that at their core is usually some form of continuous integration (CI) technology. As one of the most widely used forms of continuous integration, Jenkins is being deployed by many leading edge IT organizations. The challenge that many average IT organizations often face is they don’t have the expertise required to implement Jenkins in the first place.

To address that issue, CloudBees today unfurled an implementation of the open source Jenkins CI platform, dubbed CloudBees Jenkins Platform - Private SaaS Edition, specifically designed to manage instances of the OpenStack private cloud computing environment on the Amazon Web Sevices (AWS) public cloud.

Andre Pino, vice president of marketing for CloudBees, says that while interest in all things DevOps is running high, adopting best practices in the form of DevOps is not a flip-of-the-switch kind of thing in most IT organizations. Rather, it’s a journey that requires a fair amount of planning on the part of a CTO or enterprise architect. To facilitate that transition, however, Pino says CloudBees Jenkins Platform- Private SaaS Edition, provides a turnkey approach to implementing continuous integration regardless of where applications are being built using a framework hosted in the cloud by CloudBees.


The CloudBees service itself takes advantage of Docker containers and Mesos data center operating system software to provide the foundation for implementing Jenkins as a service, adds Pino.

When it comes to DevOps, most organizations find themselves in one of those classic chicken-and-egg conversations. In an ideal world, a well-defined DevOps framework would be in place to enable the organization’s IT culture to evolve. In reality, most IT organizations need some exposure to tools before the culture can begin to evolve. Making CI available as a service is as good a place to start making that cultural transition as any.

Add Comment      Leave a comment on this blog post
Aug 18, 2016 10:29 PM vadmin vadmin  says:
Thank you very much ! You have cleared out the difference between them. Reply
Mar 7, 2017 1:23 AM DevOps Consult DevOps Consult  says:
Hi, Nice and Valuable information you explained in this article I loved it more, it useful for me a lot. Thanks for sharing this article. Reply

Post a comment





(Maximum characters: 1200). You have 1200 characters left.




Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.