VictorOps is now Splunk On-Call! Learn More.
Continuous delivery (CD) and continuous improvement (CI) are established realities for many teams. For others, these concepts represent a significant milestone on their DevOps and Agile journey. As teams adopt tools that enable CI/CD, they often forget the impact of high change rates on infrastructure and on-call teams. How you manage communication, work streams, and context across teams is a significant indicator for success.
As teams begin to deploy faster and faster, the reality of CI/CD can be fraught with risk to system reliability. Deployments represent state changes to systems, as do feature flags, a/b tests, and more. As those change rates increase, so does the likelihood that an incident response team will be left diagnosing a moving target. Accounting for all of the changes that can be introduced is enough to give anyone a nervous breakdown.
On January 25, 2018 we explored multiple approaches to providing communication and context to an on-call team while enabling adoption of greater velocity and change for their application teams. We addressed incident management practices at different team maturity levels and the ways in which teams move from beginner, to intermediate, to advanced in their approaches to handling incidents and contextual data as they improve their CI/CD practices.
Specifically, we discussed:
Attendees left with a strong understanding of the path to advanced CI/CD maturity, and the phases to anticipate and manage along the way. Watch the recording of the webinar to see what else we discussed.
And if you want to see how CloudBees Jenkins Solutions and VictorOps work together, schedule a VictorOps demo.