CloudBees - 2019 DevOps and Jenkins Community Report

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 Scientist
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.

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).

In 2017,

CI is relatively pervasive, with 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

Unlocking the flow of value

Automation is a key enabler of DevOps.

Upstream activities are more likely to be automated

automate build, up from in 2017

automate test, statistically equivalent to in 2017


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

automate release, up from in 2017

automate deployment, up from in 2017

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

What key downstream activities do High Velocity Practitioners automate?

automate governance

vs the average of

automate security

vs the average of

automate release

vs the average of


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 vs an average of .

People

High Velocity Practitioners collaborate.

collaborate to plan upcoming work

vs the average of

involve security during development

vs the average of

Process

High Velocity Practitioners prioritize metrics.

capture software delivery process metrics

vs the average of

automate metrics and reporting with Jenkins

vs the average of

High Velocity Practitioners who track four or more metrics experience 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

implement CI in multiple workgroups

vs the average of

This represents an overall increase from 2017

have CI fully standardized

vs the average of

This represents an overall increase from 2017

CD

implement CD in multiple workgroups

vs the average of

This represents an overall increase from 2017

have CD fully standardized

vs the average of

This represents an overall increase from 2017

How do High Velocity Practitioners use technology?

Containers

use containers

vs the average of

use Kubernetes™

vs the average of

Adoption of Kubernetes across the board is up from 2017

Microservices

use microservices

vs the average of

Cloud hosting

host Jenkins on cloud platforms

vs the average of

overall increase from 2017

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.

Deploy several times a week vs of average

Deploy once per day vs of average

Deploy multiple times per day vs of average

Deploy on every change or practice continuous deployment vs of average

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

Spend less than 25% of time on unplanned work vs the average of 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.