Case Study: Criteo reduces build failure resolution time with Gradle Develocity

How Develocity customer Criteo reduced time-to-resolution for build failures from 30 minutes to 30 seconds

Criteo, a publicly-traded online advertising provider, faced significant developer productivity challenges in its complex, polyglot development environment. With thousands of builds daily across numerous projects, troubleshooting failures was a major pain point. Their team struggled to efficiently diagnose issues, a process that could take up to 30 minutes, hindering their ability to maintain a high level of service across different tech stacks.

By implementing Develocity from Gradle, Criteo gained deep observability into their build and test processes. The solution's Build Scans became the primary reporting tool, allowing developers to instantly pinpoint failures and compare dependency changes. This enabled Criteo to reduce their average time-to-resolution for build failures from 30 minutes down to just 30 seconds, dramatically improving developer productivity and experience.

Criteo

Loïc Teikiteetini-Vaysse

Staff DevOps Engineer