Keeping your team’s Gradle builds in top shape
summary
Automated build validation scripts run five reproducible experiments (up-to-date, local cache, relocatability, CI→CI, CI→local), produce paired build scans and copied artifacts, and identify which tasks actually cause cache misses. A GitHub Action runs them weekly. The new Gradle Enterprise API lets code fetch ~200 public builds (filtered to ~85), compute per-task negative avoidance savings, and pinpoint that dex merging is usually worth caching but shows cache misses and slowdowns for Android test variants, guiding targeted fixes.
AI-written summary · about
chapters (11)
- 0:00Introduction and speakers
- 2:18Why developer productivity matters
- 4:25Build scans and Gradle Enterprise
- 6:17What is build caching
- 7:42Build validation scripts
- 18:43Automating build validation
- 19:25Gradle Enterprise API overview
- 21:52Is my task worth caching
- 29:16Using Gradle Enterprise API
- 33:50Room annotation processor issues
- 34:55Call to action and resources
related talks
33mKeeping your Gradle builds in top shape
30mAndroid Developer Productivity
37mImproving developer productivity with Gradle Enterprise in 2023
36mImproving Gradle Builds
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
54mFrom Laptop Builds to Advanced CI
01h 39mWorkshop: Maximize Developer Productivity with Fast and Reliable Gradle and Maven Builds
28mMaking the most of your Gradle Builds
