CloudBees - The Pipeline to DevOps

Sometimes a combination of market forces, technology changes and people coalesce into a rare opportunity. That is happening for CloudBees now.

DevOps has been hot for the past few years, but the recent 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).

It is not an exaggeration to compare Kohsuke with Henry Ford for creating the equivalent of the software assembly line. The DevOps "Pipeline" is the software assembly line. At one end, developers write code and share and store that in GitHub. The basic function of Jenkins is to watch code repositories like GitHub for changes. And on each change any of the developers makes, go thru the whole process of taking that code thru the laborious and complex process of making it into a running application.

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!

Comments

Post a Comment

Popular posts from this blog

Ringside Winding Down

A year ago, a group of us met in a pizza parlor to discuss how we could bring the social web to every website and business. In January, we launched Ringside Networks with seed funding from Matrix Partners, one of the best VC firms in the country. By the end of March we released into open source an initial beta of our Social Application Server – a very ambitious project. We got some very positive reviews on our approach, our implementation and the need in the marketplace for every website to become social. We were ready for our Series A round of funding, and in late May we received a number of term sheet offers from the very best VC firms. As we were about to finalize our funding, one of the biggest non-evil Internet companies asked if we would have interest in being acquired instead. After a lot of thought and debate, we decided that the larger company would enable us to get our technology to market sooner and with more impact. The story sounds almost too good to be true. And it w...
Read more

Capitalism vs. the Three Legged Stool

Image
Wikipedia defines: " Capitalism  is an  economic system  in which trade, industry and the  means of production  are controlled by private owners with the goal of making  profits  in a  market economy ." This definition has always bothered me. I prefer a different model where there is equal recognition of the three primary drivers behind the success of a company: Owners Employees Customers I like to think of it as a three legged stool, where each leg is as important as the other.  One gets too large or small and the stool tips over. The free market is supposed to take care of Employees and Customers.  Employees because the Owners will create so many jobs that due to supply and demand, employees will receive competitive pay.  Customers because if the owners are not building the right thing, then they can go elsewhere. As someone who has helped to build about 10 startup companies now, I have seen the power in mak...
Read more

Galbraith Revisited

Image
To follow up on my post from a while ago, Galbraith sited 5 key reasons for the 1929 crash and following depression: 1. The bad distribution of income. 2. The bad corporate structure. 3. The bad banking structure. 4. The dubious state of the foreign balance. 5. The poor state of economic intelligence. To compare this to today: 1. Bad income distribution. 1929 - Top 5% received about 33% of all personal income. 1929 - Top 1% held 44% of all wealth. 2000 - Top 1% received about 20% of all personal income. 2004 - Top 1% held 34% of all wealth. Here is a picture of the real income gains between 1979 and 2005 by percentage. It is clear that the top income groups are gaining ground faster than lower income groups - creating an income distribution that approaches 1929. 2. Bad corporate structure. In the 1929 era there had been a large rise in a "vast structure of holding companies and investment trusts... In particular the dividends from the operating companies paid the interest on t...
Read more