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.
In 2017,
CI is relatively pervasive, with
CD is less prevalent, but the year-over-year growth shows significant traction.
Upstream activities are more likely to be automated
automate build, up from
automate test, statistically equivalent to
Downstream activities, although less likely to be automated, show significant year-over-year increase
automate release, up from
automate deployment, up from
High Velocity Practitioners automating upstream and downstream are
vs the average of
vs the average of
vs the average of
High Velocity
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 the average of
vs the average of
vs the average of
vs the average of
High Velocity Practitioners who track four or more metrics experience
implement CI in multiple workgroups
vs the average of
This represents an overall
have CI fully standardized
vs the average of
This represents an overall
implement CD in multiple workgroups
vs the average of
This represents an overall
have CD fully standardized
vs the average of
This represents an overall
vs the average of
vs the average of
Adoption of Kubernetes across the board is up
vs the average of
vs the average of
Deploy several times a week vs
Deploy once per day vs
Deploy multiple times per day vs
Deploy on every change or practice continuous deployment vs
Spend less than 25% of time on unplanned work vs the average of
