Operations | Monitoring | ITSM | DevOps | Cloud

The Agile software development lifecycle was designed to surface problems early, with short sprints, iterative testing, and continuous integration built on the premise that faster feedback loops produce better software. AI coding tools have changed the velocity equation across every phase of that loop, but the phases designed to catch failures are struggling to keep up because build speed and validation capacity have not accelerated at the same rate, and the gap between them is widening with every sprint.

In January we launched Tests in Bitbucket Pipelines – a single place to track, organize, and understand your test health over time. In April we added automatic flaky test detection so unreliable tests get flagged before they slow your team down. But spotting a problem is only half the battle. Day to day, your team still needs to act on a test – track it as work, clean it up, or route it to the right person.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey toward autonomous operations. Read on to learn about the PagerDuty agent app in GitHub (Early Access) and how it builds toward this vision. How many tabs do you have open right now? And how many more do you open the moment an incident hits? Context switching during incident response is one of the most persistent sources of toil in engineering.