Our favorite VP Product Chen Harel gave an outstanding talk this year at Jenkins World so, naturally, we want to share it with all of you! (Skip to the bottom to watch right away.)
During his session, Chen addresses the issues that most of us are facing that lead us to Sev1 Situation Rooms and poses the question – if, given the right data, we can actually prevent those issues from ever happening at all (in production).
With speed and stability at odds in the software development lifecycle, the cost of poor quality software in 2018 was enormous and many teams suffer from frequent Sev1 issues that impact customers and the company’s bottom line.
To address these issues, organizations have implemented “you build it, you run it” workflows to increase accountability and have started to “shift left” to focus on quality earlier in development.
Regardless of the steps companies take to address these issues, there is one thing that doesn’t change from company to company. Good data is required to measure and track quality over time.
Without giving too much away, here are the steps of the scoring process that Chen goes over in the session (To skip straight to this part, start the video at 8:06):
- Detect all errors and slowdowns
- Classify each event
- Prioritize by severity
- Score the build
- Block builds
- Visualize the data
Watch the video to get the full scoop on OverOps’ formula for blocking Sev1s from production!
For more information about the OverOps Jenkins integration, visit our website!
Achieving Observability: How to Address the Unknown Unknowns in Your Application
Subscribe for Post Updates