This information would be helpful when answering questions from developers like "why was the cache entry discarded when gradle says it had no issues storing the cache?"
Expected Behavior
Run a build with configuration cache enabled, and a task that is incompatible:
./gradlew myIncompatibleTask --configuration-cache
Gradle will say it had no issues storing the cache, but then say the cache result was discarded. This is fine. However, Gradle will also include a configuration cache report. That report should tell the reader why the cache result was discarded.
Current Behavior
The report does not explain why the cache result was discarded.
Context
See also https://gradle-community.slack.com/archives/C013WEPGQF9/p1658176464418579. The alternative is having an expert you can ping in Slack to ask why a given build did what it did. Not very scalable! :)
This information would be helpful when answering questions from developers like "why was the cache entry discarded when gradle says it had no issues storing the cache?"
Expected Behavior
Run a build with configuration cache enabled, and a task that is incompatible:
Gradle will say it had no issues storing the cache, but then say the cache result was discarded. This is fine. However, Gradle will also include a configuration cache report. That report should tell the reader why the cache result was discarded.
Current Behavior
The report does not explain why the cache result was discarded.
Context
See also https://gradle-community.slack.com/archives/C013WEPGQF9/p1658176464418579. The alternative is having an expert you can ping in Slack to ask why a given build did what it did. Not very scalable! :)