Improving Gradle Builds
summary
Walks through benchmarking and fixing a 1,292‑module replica of a production app, showing build scans that break time into initialization configuration and task execution and pointing out an 11‑minute clean build with ~10 minutes in execution. Recommends using Gradle Enterprise for team-wide scans and tags, using Gradle Profiler to automate iterations and detect regressions, and applying plugins like dependency‑analysis, gradle‑doctor and an Android build‑cache plugin plus anvil to reduce annotation processing and improve cacheability.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:21Improving Gradle Builds
- 1:32Uber Build Eval
- 3:47Build Scan
- 9:24Build Tags
- 11:07Optimizations
- 12:25AGP Features
- 13:11Dependency Analysis Plugin
- 16:12Gradle Doctor Plugin
- 17:49Disable Remote Caching
- 18:27Android Build Cache Plugin
- 19:35Modularization
- 20:11Module Graph Assert Plugin
- 26:03Version Catalogs
- 27:58Gradle Profiler
- 31:09Performance Scenario
- 31:46CI Pipeline
- 32:31Use Cases
- 32:50Anvil
related talks
33mIMPROVING ANDROID BUILD PERFORMANCE
41mKeeping your team's Gradle builds in top shape
31mImproving Android Build performance
37mThe Build Shrugged
36mImproving Android Developer Experience with Gradle Build Scans
28mMaking the most of your Gradle Builds
37mBecoming and Staying a Productive Developer with Build Scans, Build Validation Scripts and Gradle
41mBreaking the build
