Jenkins is Showing the CI/CD Way

 

JetBrains just released the 2018 edition of their The State of Developer Ecosystem Survey. It is pretty interesting, as it is based on a broad-based, cross-section of more than 6,000 developers and, as such, is likely to be a very good proxy of the market.

The survey analyzes multiple sectors, from languages to databases. Interestingly enough, continuous integration and continuous delivery are not in the “DevOps” section, but in their “Team Tools” section.

So, what do we learn?

With 62%, Jenkins is the leading continuous integration tool, period! Even if you sum up the percentage of the next four followers (!), you don’t reach the level of Jenkins.

Jenkins is the leading continuous integration tool

 

If you then split cloud vs. on-premise usage, the result is the same: Jenkins is the de facto continuous integration tool, well ahead of any competition. In the cloud usage category, adding Codeship (and, for some mysterious reason a second CodeShip, with a wrong spelling), puts the CloudBees ecosystem above 60%. In on-premise usage, the CloudBees ecosystem is even higher, at 66%.

Jenkins is the de facto continuous integration tool

 

As companies get serious about continuous integration and continuous delivery, it becomes obvious to all of them that they won’t get an overall increase in velocity and productivity if they solely focus on new applications: they need to build their DevOps muscle across the entire organization. As such, their CI/CD solution must integrate with a LOT of different tools, systems and environments. This is a key area where Jenkins shines, obviously, with more than 1,400 plugins!

And that’s typically where CloudBees comes into the picture. Once you move from a relatively well-contained Jenkins setup (typically an overloaded Jenkins master, set up years ago by a Jenkins aficionado) to a company-wide practice, concepts such as self-service, management at scale, collaboration, governance and security will emerge as key conditions for a successful enterprise-wide adoption of DevOps. From on-premise to the cloud, from self-managed to self-service, from opinionated to fully customized, as the CI/CD Power House, we have the solution that fits your requirements and the enablement services to help you.

Onward,
Sacha

 

Sacha Labourey
CEO and co-founder
CloudBees

A native of Switzerland, Sacha graduated from EPFL in 1999. At EPFL, he started Cogito Informatique, an IT consulting business. In 2001, he joined Marc Fleury’s JBoss project as a core contributor, implementing JBoss’ original clustering features. He went on to become GM for JBoss Europe, leading the strategy and helping to recruit partners that fueled JBoss’ growth. In 2005, he became CTO and oversaw all of JBoss engineering. In June 2006, Red Hat acquired JBoss. As CTO, Sacha played a crucial role in integrating and productizing the JBoss software with Red Hat offerings. In 2007, Sacha became co-General Manager of Red Hat’s middleware division. He left Red Hat in 2009 and founded CloudBees in March 2010. Follow Sacha on Twitter.