Keeping your Gradle builds in top shape

on YouTube ↗33m

" summary

Company builds lose an estimated 42 hours per day when each developer wastes 60 seconds across 50 builds; a five-step build validation scripts suite runs two clean and non‑clean builds (plus cross‑directory and CI checks) to pinpoint cache misses, timestamps and absolute‑path issues. A GitHub Action automates weekly runs. A REST Gradle Enterprise API plus OpenAPI codegen produces Kotlin/Retrofit clients to query build durations, cache performance and users with negative avoidance savings (e.g. 40 MB test artifact causing slow cache pulls).

AI-written summary · about

" chapters (10)

1. 0:00Introduction and background
2. 6:29Build caching overview
3. 7:53Build validation scripts
4. 16:22Local and CI cacheability
5. 19:52Automating validation scripts
6. 21:36Gradle Enterprise export API
7. 23:21New Gradle Enterprise API
8. 26:10Analyzing build performance
9. 30:48Gradle Enterprise Android features
10. 32:11Resources and Q&A

" related talks

• 41mKeeping your team's Gradle builds in top shapeNelson Osacky · droidcon London 2022
• 36mKeeping your team’s Gradle builds in top shapeNelson Osacky, Inaki Villar · droidcon New York 2022
• 30mAndroid Developer ProductivityNelson Osacky · droidcon San Francisco 2022
• 40mNail your Gradle build timeJosef Raska · droidcon Berlin 2021
• 37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and GradleNelson Osacky, Etienne Studer · Droidcon London 2023
• 37mImproving developer productivity with Gradle Enterprise in 2023Nelson Osacky, Julio Zynger · droidcon Berlin 2023
• 36mImproving Gradle BuildsMohit Sarveiya · Android Worldwide 2022
• 40mBuild times breaking your flow? Learn how to make them fast!Louis Jacomet · droidcon London 2025