Disable configuration cache in the CI by default #3601
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Content
Disable configuration cache for all Gradle CI jobs.
Motivation and context
Gradle configuration cache can be a nice trick to speed up builds, but it's also a bit unstable.
While locally we can just re-run a task with
--no-configuration-cache
or disable theorg.gradle.configuration-cache
Gradle property, in the CI we can't do that to fix a flaky job running with a mismatched config cache and we've seen several of those already, so I'm disabling the cache in the CI for now.Tests
The CI should just pass.
Checklist