2019 DevOps and Jenkins Community Report

A Letter
from Kohsuke

Whether you call it continuous integration, DevOps, or continuous delivery, the Jenkins® community has always been with the practitioners who go through this difficult, never-ending journey toward better software delivery. If you are going through that journey, I’d imagine you might be feeling lonely and frustrated sometimes. The journey might feel never-ending; some people around you might not share your sense of urgency.


That’s why I’m so excited to share our 2019 DevOps and Jenkins Community Report, based on the fifth survey of the community. This gives you the objective view into where everyone is on this journey, and they share the same struggles as you. If you are ahead on the journey, this survey is a celebration of your achievement. If you are behind on the journey, this survey gives you more ammunition to convince people around you what you knew all along.


And regardless of where you are on this journey, my sincere thanks for pushing this ball forward and making an impact to the world. This survey is just a small token of appreciation, in the hope that it helps you travel this journey further.

Best regards,

Kohsuke Kawaguchi
Chief Technology Officer
CloudBees, Inc.

Growth Trends
in DevOps

The fifth DevOps and Jenkins Community Survey, conducted by CloudBees, captures best practices and trends in DevOps adoption and maturity across over 1,000 Jenkins users.

67% of respondents say they’re practicing DevOps

Defending
against DevOps
washing

To effectively practice DevOps requires practicing both continuous integration (CI) and continuous delivery (CD).

67% Report practicing DevOps, but only

 

67%

49% practiced CD

 

49%

In 2017,

47% Report practicing DevOps, but only

 

47%

38% practiced CD

 

38%

CI is relatively pervasive, with 81% practicing this year.
CD is less prevalent, but the year-over-year growth shows significant traction.

What does it look like to do DevOps well?

High Velocity Practitioners use the following key practices:

End-to-end automation throughout the entire software delivery pipeline

High levels of collaboration with functional teams outside development

Automated capture of key DevOps metrics for visibility

For this analysis we scored respondents based on DevOps maturity measures. These indicators include deployment frequency, depth of automation, deployment approach and cross-functional collaboration. Respondents were then categorized using the IQR method. The top 25% are referred to as High Velocity Practitioners.

Unlocking the flow of value

Automation is a key enabler of DevOps.

Upstream activities are more likely to be automated

 

95%

automate build, up from 74% in 2017

 

88%

automate test, statistically equivalent to 93% in 2017

Downstream activities, although less likely to be automated, show significant year-over-year increase

 

64%

automate release, up from 18% in 2017

 

68%

automate deployment, up from 41% in 2017

High Velocity Practitioners automating upstream and downstream are 14% more likely to have a Jenkins installation with over seven masters, and 21% more likely to have over seven build agents.

What key downstream activities do High Velocity Practitioners automate?

30% automate governance

vs the average of 18%

38% automate security

vs the average of 23%

84% automate release

vs the average of 63%

High Velocity

vs

Average

High Velocity Practitioners who automate security and involve the security team in development do not see a negative impact on deployment frequency. Practitioners with integrated security practices deploy once per week or more, at a rate of 88% vs an average of 56%.

People

High Velocity Practitioners collaborate.

99% collaborate to plan upcoming work

vs the average of 74%

67% involve security during development

vs the average of 51%

Process

High Velocity Practitioners prioritize metrics.

84% capture software delivery process metrics

vs the average of 66%

50% automate metrics and reporting with Jenkins

vs the average of 35%

High Velocity Practitioners who track four or more metrics experience 8% less unplanned work than those who track no metrics at all.

High Velocity Practitioners are more likely to scale CI/CD beyond a single team.

CI

 

40%

implement CI in multiple workgroups

vs the average of 39%

 

30%

This represents an overall 30% increase from 2017

 

51%

have CI fully standardized

vs the average of 35%

 

29%

This represents an overall 29% increase from 2017

CD

 

44%

implement CD in multiple workgroups

vs the average of 35%

 

25%

This represents an overall 25% increase from 2017

 

32%

have CD fully standardized

vs the average of 18%

 

12%

This represents an overall 12% increase from 2017

How do High Velocity Practitioners use technology?

Containers

79% use containers

vs the average of 65%

58% use Kubernetes™

vs the average of 47%

Adoption of Kubernetes across the board is up 235% from 2017

Microservices

63% use microservices

vs the average of 41%

Cloud hosting

97% host Jenkins on cloud platforms

vs the average of 73%

49% overall increase from 2017

80% of High Velocity Practitioners running Jenkins on containers in a cloud environment commit code to trunk more than once per day, vs the average of 60%.

DevOps benefits realized by High Velocity Practitioners

High Velocity Practitioners deploy more often than average, enabling them to iterate more, gain rapid feedback and recover faster.

 

30%

Deploy several times a week vs 18% of average

 

6%

Deploy once per day vs 4% of average

 

18%

Deploy multiple times per day vs 9% of average

 

15%

Deploy on every change or practice continuous deployment vs 10% of average

High Velocity Practitioners spend less time on unplanned work, allowing increased productivity, reduced DevOps waste and more satisfied developers.

 

61%

Spend less than 25% of time on unplanned work vs the average of 48% of time

End-to-end automation clears the path to success

High Velocity Practitioners and their teams transform their software delivery pipelines by tuning people, process and technology to model DevOps best practices. By truly embracing DevOps with CI and CD, you can implement end-to-end automation and bridge functional silos, resulting in higher velocity, higher stability, more productive developers and ultimately a more competitive business.

Explore how end-to-end automation of software delivery can propel your team's success – get started with CloudBees.

CloudBees, Inc.
2001 Gateway Place, Suite 670W | San Jose, CA 95110 | United States
www.cloudbees.com | info@cloudbees.com
The registered trademark Jenkins® is used to pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at: www.cloudbees.com/jenkins/about
© 2019 CloudBees, Inc. CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Jenkins Solutions, CloudBees Jenkins Enterprise, CloudBees Jenkins Team, CloudBees Jenkins Operations Center, CloudBees Jenkins Advisor and DEV@cloud are trademarks of CloudBees, Inc. Other product or brand names may be trademarks or registered trademarks of their respective holders.
0219v00