The configuration cache is a feature that significantly improves build performance by caching the result of the configuration phase and reusing this for subsequent builds.
Implementing support for the configuration cache in this plugin would improve users experience.
See https://docs.gradle.org/nightly/userguide/configuration_cache.html
The configuration cache will be introduced in Gradle 6.6.
But this can already be tested using 6.6-milestone-2.
I tried running assemble with a Gradle 6.6-milestone-2, com.google.firebase:firebase-crashlytics-gradle:2.2.0 and the configuration cache enabled.
The first time it works because the configuration is not from the cache but when "Reusing configuration cache" it breaks the build with:
No such property: resourceFile for class: java.lang.Object
It would just make every build faster.
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Thanks for the feature request. This is on the roadmap. We'll use this issue for comms going forward.
Gradle 6.6 released
Kotlin 1.4 in RC
AGP 4.1 RC 1
it seems tools are going to be GA soon, even if the feature will be still experimental, and this plugin seems to be the only blocker for use configuration-cache while developing (we can do hacks to not apply the plugin if we are not at CI, but it's the kind of thing that someday will break something and loosing the crashes from Production is too risky)
Sorry to bother you again, all the tooling to user Configuration Cache is ready in stable versions, and this issue is the only one preventing users to adopt Configuration Cache.
Is there any progress or ETA?
com.google.firebase:firebase-crashlytics-gradle:2.4.1
still has the same issue
Most helpful comment
Thanks for the feature request. This is on the roadmap. We'll use this issue for comms going forward.