Plugging Into the Gradle Matrix
summary
Large monorepos are real: one repo has ~4,000+ Gradle modules and ~4 million LOC supporting ~170 active developers, another about 800 modules. The talk shows concrete fixes: switch from create to register your task and use Provider APIs to avoid eager configuration, cut ~290 unnecessary task realizations in one plugin, survive a 30% configuration regression from composite builds by publishing build logic, adopt configuration avoidance and configuration cache to save ~5,400 developer hours per year.
AI-written summary · about
chapters (17)
- 0:00Introduction and speakers
- 1:08What is a Gradle plugin
- 4:40Configuration avoidance in plugins
- 7:52Task dependencies and providers
- 12:27Task dependencies and Android variants
- 16:24Worker API and build services
- 19:15Real-world plugin examples
- 24:30Why Gradle best practices matter
- 25:13Convention plugins explained
- 28:22Kotlin DSL vs Groovy in builds
- 30:51Dependency analysis plugin case study
- 33:36Managing plugin dependencies
- 35:22Testing Gradle plugins
- 36:05Functional testing with Spock
- 39:14Caching and task design patterns
- 40:17Configuration caching benefits
- 41:01Project isolation and closing
related talks
40mSimple Recipes to Enhance Developer Productivity
37mBuild bigger, better: Gradle for large projects
26mGoodness, Gracious, Great Builds of Gradle
43mThe Engineering Playbook for Growing Android Teams
01h 00mAndroid builds
32mGradle Convention Plugins
30mModular Android Development
37mEmbracing Declarative Gradle and Software Types