As you saw in other posts, CloudBees has acquired Codeship. With this, CloudBees strengthens its position as the leader in CI/CD by serving the entire spectrum from large to small, and from on-prem to cloud, regardless of whether you develop embedded software, web services or mobile games. This is an exciting development for me, as CTO of CloudBees.
As a founder of Jenkins, I’m also just as excited, for I firmly believe that this is a rather positive development for Jenkins as well. Let me explain.
First of all, CloudBees’ commitment to Jenkins has NOT changed. If anything, we are doubling down. The Jenkins project is still on the never-ending streak of growth after 10+ years. Just in the time period of November 30, 2016 - November 30, 2017, usage has increased about 20%, and the Jenkins business for CloudBees is growing even faster than that. As a simple matter of fact, Jenkins plays the biggest role to the success of CloudBees.
So this year, we plan to put more people than ever to work on Jenkins, to take on important projects that we haven’t been able to take on before. Some of this is already in progress, like configuration as code, and a number of even more exciting projects will follow soon. All of those will be well underway by our annual Jenkins World, which you can already register for, and I’m already worried about how to talk about all of them in the time I will get for my keynote.
Now, with Codeship, CloudBees intends to build a portability bridge that allows projects to migrate between two worlds — the on-prem world where Jenkins really excels, and the cloud world where Codeship really excels. Codeship complements Jenkins in an area where Jenkins has not been focused. This makes both Jenkins and Codeship an even more obvious and safer choice for existing and new users alike.
The combination of the two is also a great opportunity to combine the speed of innovation, which is the key strength of open source, and the ease of use and simplicity, which is the key strength of Software as a Service. I know the cross pollination of these two cultures will start in CloudBees and spread to the broader Jenkins community.
In summary, CloudBees continues to believe that the incredibly valuable ecosystem of Jenkins is a key to its success. Vice versa, Jenkins continues to benefit from the leadership and the contributions coming from CloudBees. The closer we can align the interests of the two, the better off they both are, and right now, I feel that this alignment is better than ever. 2018 will be an exciting year for Jenkins.
CTO at CloudBees and Jenkins founder