CloudBees is an active participant in the Jenkins community and plays a significant role in moving the Jenkins continuous integration (CI) open source project forward. Over the years, CloudBees has focused its business on providing premium enterprise editions on top of the open source core.
Last week, the open source project and CloudBees announced the extension of Jenkins into deployment with new integrations that allow its users to utilize lightweight Docker containers for infrastructure with microservices-based architectures for applications, and continuous delivery for application lifecycle management. In December 2014 CloudBees introduced its Workflow plugin that facilitates continuous delivery with Jenkins.
Jenkins made its first major step from continuous integration to continuous delivery (CD) with the December 2014 announcement of Jenkins Workflow, which enables CD pipelines to be created and managed. Jenkins has become a ubiquitous CI tool embraced by organizations and development teams of all sizes. It originated as a community fork from Hudson, the original open source project in 2011, and its adoption trajectory has been upward as Hudson use declines.
Jenkins is already a core component of many enterprise DevOps solutions, and its extension to deployment orchestration completes the pipeline that it initiates. This evolution of Jenkins, which plays a pivotal role in the DevOps ecosystem, will cause release-management and automation-tool vendors some discomfort as it erodes their territory while playing a “co-opetition” role. The ripple effect will see the entry cost to a full CD solution drop, allowing for wider adoption of DevOps. DevOps solution players will need to improve their offering to maintain market share, and one way of doing this would be to provide integration with test and application performance analytics.
CloudBees enterprise services launches CloudBees Jenkins Platform
CloudBees also launched the CloudBees Jenkins Platform this week, which combines the company’s CloudBees Enterprise Jenkins and Jenkins Operation Center products in a single solution for managing complex multi-server installations, with the Team Edition for smaller installations, and the full Enterprise Edition that enables large distributed teams to operate with high efficiency. The new platform will run on-premise or on public clouds, and has been made available on Amazon Web Services (AWS) EC2, offering enhanced elasticity and integration into AWS services. Customers of the platform will gain professional support, high availability, security, and core features, as well as the CD offering.
CloudBees as a company has made the transition from being a PaaS player to being primarily a Jenkins solution provider, riding on the popularity of the tool. Its evolution of Jenkins will now see it emerge as a key DevOps player.
Microservices and Docker gain further support from Jenkins
The rise in adoption of Docker follows the increasing interest in microservices architecture, which in turn is being driven by agile and DevOps practices. Jenkins processes can be initiated by changes in Docker containers, and CloudBees has announced six new open source software plugins for Docker. One plugin is Docker Workflow, which provides support for Jenkins Workflow to build CD pipelines for containerized applications. The support for Docker from Jenkins will add to the usability of containers and microservices and will be welcomed by DevOps developers.
Michael Azoff, Principal Analyst, Ovum Infrastructure Solutions Group