Speeding up inner dev loop with Gradle Configuration Cache
summary
Demonstrates that enabling Configuration Cache and fixing serialization issues cuts configuration time from over 15 seconds to about 1 second on their example build and can drop repeat runs to tens of milliseconds once tasks are adjusted. Walks through concrete fixes: avoid capturing project or Configuration objects, switch to file collections and Provider API, use the configuration cache report and dry run to find errors, mark noncompatible tasks, and optionally use the commercial product Velocity for cross‑machine caching and observability.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:47Inner dev loop speed
- 3:11Gradle build lifecycle
- 4:13Optimizing execution phase
- 5:36Gradle Configuration Cache
- 8:50Adoption and benefits
- 9:31How it works
- 14:48Adoption steps
- 16:54Common issues demo
- 25:54Fixing compatibility
- 31:42Final enablement steps
- 32:03Parallelism and work avoidance
- 35:15Improving hit rates
- 39:04Tracking usage
- 40:09Future plans
- 41:12Conclusion & Q&A
related talks
02h 42mHeading to Gradle 9
41mKeeping your team's Gradle builds in top shape
05mOver the Ant Hill to Gradle
01h 03mKey Gradle Concepts And Practices
48mWhat's new in Gradle 5?
42mTechniques for a faster JVM start-up
01h 01mGradle 3.0 and beyond
48mCaching the Spring Context in Tests: How to Speed Up Testing