significantly improves build performance by caching the result of the configuration phase and reusing this for subsequent builds. org.gradle.configuration-cache=true
belonging to different subprojects in parallel with org.gradle.parallel=true Gradle worker API allows parallel within project tasks, but non-trivial to migrate to org.gradle.configuration-cache=true all tasks parallel by default
FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':myTask'. > Cannot fingerprint input property 'inputCustomType': value 'Build_gradle$CustomType@d00c052' cannot be serialized.
graph as configuration cache cannot be reused because an input to plugin 'com.android.internal.library' has changed. https://issuetracker.google.com/issues/285320724
to go from WARN to ERROR - Reported and helped fix dozens of bugs in Gradle, Android Gradle Plugin, Kotlin Gradle Plugin, Protobuf Gradle Plugin, SPDX Gradle Plugin - Fixed dozens of issues within our own build logic - Upgrades to plugins still can come with regressions (e.g. KGP 2.0.0) → test, report and nudge AndroidX Adoption of Configuration Cache
- Once you get it working, you will not want to go back - If you enable CC in CI, store configuration cache reports for debugging - Bring down configuration cache report entry count to a minimum - Once CC is enabled you’ll notice task performance more (👋 CompileKotlin) - It will not help Gradle Sync in Android Studio / Intellij