Keeping your team's Gradle builds in top shape
summary
Shows concrete fixes and tools: run the build validation scripts (five reproducible experiments) to catch up-to-date, local-cache, relocatability and CI-cache issues; Android X runs ~2,000 builds/week with median 2m17s; Room annotation absolute paths cause cache misses in ~80% of Android projects seen; a 60s waste at 50 builds/day for 50 devs equals ~42 lost hours/day; automate checks with a GitHub Action, use Gradle Enterprise build scans and the new REST API to find slow users, negative cache savings, and flaky tests.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 4:24Gradle Enterprise overview and demo
- 7:54Build caching fundamentals
- 9:19Build validation scripts explained
- 19:11Advanced caching experiments
- 24:33Gradle Enterprise export API
- 27:00Automating API clients with OpenAPI
- 30:54Ranking builds by performance
- 31:57Finding negative cache savings
- 34:04Monitoring build cache errors
- 34:45Android-specific Gradle features
- 36:08Room cache myths and fixes
- 37:54Resources and Q&A
related talks
33mKeeping your Gradle builds in top shape
30mAndroid Developer Productivity
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
36mImproving Gradle Builds
36mImproving Android Developer Experience with Gradle Build Scans
31mImproving Android Build performance
32m5 ways to improve your Android build productivity
37mImproving developer productivity with Gradle Enterprise in 2023