Session Description

Enterprises everywhere are focused on increasing velocity of software delivery. But with short, frequent release cycles, code quality is often compromised. As the first line of defense for software quality and customer experience, development, DevOps and QA teams are expected to prevent code defects from escaping into production. Yet, they also need to manage unprecedented workloads with minimal time and resources.

The fact that most organizations still encounter significant production errors at a regular cadence speaks to shortcomings in many of today’s quality processes. To address these gaps, we’ve identified five critical quality gates – static analysis, new errors, critical exceptions, resurface errors and unique error count – you can build into your CloudBees pipeline using an open source Jenkins plugin to clearly determine if a release is safe to be promoted.

In this session, we’ll delve into some of the common challenges and problems with current QA methods, then define and walk through each quality gate, including examples of how they work, best practices for configuring thresholds and where to access the necessary open source resources. Attendees will walk away with a clear understanding of the five quality gates, how they can fill quality and testing gaps left by existing tools and processes and the open source resources available to build these gates into their own CI/CD tooling.