DevOps World | Jenkins World 2019 San Francisco

Most organizations who adopt an agile approach to development and testing face a common challenge: How do I increase development velocity without allowing critical errors to slip past into production? The expression “separate the signal from the noise” comes up often, but when build processes continue to get louder and louder -– more errors, more alerts, more logs to sift through -– finding the one anomaly that actually risks introducing a SEV1 issue can be a seemingly impossible feat. This was a problem our team encountered when tracking our own builds. We captured data about billions of events happening every day, without a quantifiable way of knowing what to prioritize and how reliable our builds actually were. Our R&D team set out to devise a formula for assessing the reliability of a build across the release pipeline. This session will walk attendees through an open source scoring system in Grafana and Jenkins that takes into account new errors, increasing errors and slowdowns to provide DevOps teams with a formulaic approach to understanding the stability of their releases -– before they go into production.