The Benevolent Gradle Overlord: Keeping Order
summary
Shows how convention and binary plugins reduce build.gradle churn and how a strict build.json schema limits knobs to allowed toggles; demonstrates enforcement techniques from Gradle property API to afterEvaluate workarounds and custom tasks that validate merged manifest (e.g. minSdk >= 24) or forbid dependencies. Describes daily shadow jobs that run nightly Gradle/KGP/AGP checks and per-commit AGP tests, a rule to automate fixes after three occurrences, and examples of successes and a rolled-back lint JDK change.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:53Reducing build complexity
- 10:34Enforcing build configs
- 16:05Extreme build.json
- 19:33Managing upgrades
- 27:11Automating bug reduction
- 30:40Monitoring build impact
- 34:08Key takeaways and conclusion
related talks
26mGoodness, Gracious, Great Builds of Gradle
32mGradle Convention Plugins
42mWriting your own Gradle Plugin: A Deep Dive
44mA Healthy Dose of Gradle
56mDeep Dive into the Android Gradle Plugin
36mMusical Chairs with Gradle: Surviving the Build Party
39mAndroid Gradle Plugin internals
28mEffective Gradle Scripts for Android Projects