Why did my build fail? Using AI to troubleshoot faster with Failure Summaries

Most developers tell us that working with CI is frustrating in large projects. Making a change in large projects can generate hundreds of builds with various types of failures—not to mention overall background flakiness. When something goes wrong, troubleshooting issues requires manually navigating several UIs and many large log files. This is where "Failure Summaries", an upcoming Develocity feature, comes in to save the day. Built in-house for Gradle engineers, Failure Summaries use AI for categorization and clustering to determine which tests are primarily responsible for a number of failures. In this session with Laurent Ploix, Senior Product Manager at Gradle, you'll see how Failure Summaries can streamline troubleshooting with a deep dive into how to distill complex test failures.