CloudBees - The Pipeline to DevOps
GitHub acquisition by Microsoft put an exclamation point on it that reverberated in the industry and beyond.
In 1913, Henry Ford put together the idea of the assembly line to produce cars faster with higher quality.
Today, almost every business and organization on the planet is based on software at some level - to track orders, to win new customers, and even to replace old business models. And the key competitive advantage is creating better software, faster.
Several years ago, the idea of DevOps emerged - basically cutting the overhead and shrinking the time to market. Companies like GitHub were created to allow developers to share code and make changes faster.
A clever guy at Sun, Kohsuke Kawaguchi, saw a personal and organizational problem way before the DevOps revolution - back in 2004. Every time he made changes to his code, he had to go thru the laborious, manual task of compiling, building, testing and deploying his code. He created the predecessor to Jenkins to automate this. Eventually he founded the open source project Jenkins (based on a name of a fictitious Butler that took care of things for him).
Today, over 170,000 organizations across the globe use Jenkins to automate their DevOps Pipeline. At any point in time, there are over a Half a Million servers running the Pipeline to create the software all of us use for tens of millions of software projects. If you think a Ford assembly line is busy - think about the Billions of software releases flowing thru the Jenkins Pipeline.
Just like different car companies have different assembly lines with different points of automation and integration, people developing software have many different points of automation and integration. 10 different car companies will have 10 different types of seats, and 10 different companies will have 10 different types of testing tools. Since Jenkins is the defacto standard, over 1,400 tools have been integrated into the Pipeline - so each of those 10 testing tools is available to each of those 10 different customers to integrate into their pipeline.
CloudBees started as the company to take Jenkins to the enterprise. And we have met with amazing success, with many customers adopting our solutions for improved security, automation, sharing, and management. Now, companies are starting to ask for more. They realize the importance of their software factory Pipeline. They want improved speed, improved control, improved consistency and quality.
Just as the Assembly Line was the key to the flow of cars at Ford, the CloudBees Pipeline is the key to making software. To take a later day example, no manufacturing company can run today without their ERP system - enabling them to monitor and control each step of the process. As CEO's begin the realize the central role of software to their organizational success, they will need that same level of control, visibility and optimization.
CloudBees has made a series of strategic moves in the past year, bringing on key talent (including Anthony, Matt and Christina) making a strategic acquisition, and taking a leadership position in the emerging Kubernetes market. Over the coming weeks, CloudBees will make a series of exciting announcements that will further solidify our position as the Hub of DevOps. Stay tuned!