Gradle: The Build System That Loves To Hate You
summary
Android X doubles from ~400 to ~800 Gradle projects and grows Java/Kotlin from ~1M to >3M LOC while CI assemble-debug averages ~11s, but maintaining that requires ~1.5 dedicated build engineers. Coverage includes concrete pitfalls and fixes: task.create vs register (configuration vs execution), use configureEach to keep laziness, prefer providers/flatMap over dependsOn, always declare outputs and enable build cache and mark tasks cacheable, use configurations+attributes for safe cross-project artifacts, and align build classpaths (apply false in root) to share build services.
AI-written summary · about
chapters (12)
- 0:00Gradle challenges
- 1:09Gradle scalability with Android X
- 3:55Gradle task pitfalls
- 9:31Lazy vs eager execution
- 12:20Task dependencies handling
- 15:31Task output caching
- 17:39Build caching up-to-dateness
- 21:05Cross-project artifact issues
- 26:44Reusing work with build services
- 32:04Gradle problematic APIs
- 33:49Gradle settings best practices
- 35:52Q&A
