Cache once and use everywhere
summary
Claim: enabling Gradle configuration cache and a shared remote Gradle build cache (or GCS-backed remote cache) cuts wasted compile time: configuration overhead remove 30s configuration time, CI unit-test verification drops from 20 to 3 minutes, and projects move from ~30% to 80–90% cache hit. Tools used: Gradle configuration cache, Gradle build cache, Google Cloud Storage plugin, Android cache-fix plugin and AGP 7 fixes for nondeterministic inputs. Built solution: remote cache + small Gradle script fixes; result: faster incremental builds and fewer rebuilds, with some tasks still excluded from remote caching.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:51Lifecycle of build Not every compile is equal
- 5:03Gradle task execution output Execution of task can be avoided
- 14:50Benefits of cache
- 18:03Cache miss
- 25:32Gradle remote cache server How can I use?
- 29:35Cache or not to Cache Is cache a Golden Hammer?
- 31:59Lifecycle of remote cache Download and zip could be slow
- 33:26Gradle build cache
related talks
19mGetting to a green build with caching on CI
38mIteration Speeds with Gradle Configuration Cache
41mKeeping your team's Gradle builds in top shape
31mExploring Build Caching - A Practical Overview
31mImproving Android Build performance
19mCOMPILING...? HOW TO REDUCE YOUR WAIT TIMES AND "GET BACK TO WORK"
32m5 ways to improve your Android build productivity
33mKeeping your Gradle builds in top shape