BT

InfoQ Homepage Enabling a Continuous Quality Feedback Loop in Jenkins and your CI/CD Pipelines

Enabling a Continuous Quality Feedback Loop in Jenkins and your CI/CD Pipelines

Company: Backtrace

In their State of DevOps report, Dr. Nicole Forsgren, Jez Humble, and Gene Kim identify that even elite teams still spend about 50% of their time on unplanned, reactive work(1). This can be attributed to remediating CI or CD pipeline failures, security issues, defects identified by end users, customer support items, and other rework that limits the amount of time teams can spend on new work.

How can teams reduce the time it takes to detect and resolve issues that impact their ability to deliver new features?

Read our blog post, Continuous Quality Feedback Loops in CI/CD Pipelines, to learn how leading companies are improving their Mean Time To Resolution by up to 90% by taking the legwork out of data collection, indexing, and aggregation, and informing development teams exactly where their bottlenecks exist so they can quickly address them.

(1) Source: Accelerate: State of DevOps 2018: Strategies for a New Economy | Does DevOps Matter? Pg 31-32

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.