Gradle Configuration Cache on CI #1772
Merged
+13
−0
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.
And enable parallel Configuration Cache:
This needs a
GRADLE_ENCRYPTION_KEY
secret to be configured in the repository settings/secrets/actions, otherwise no configuration cache will be saved or restored.As explained in the docs, you can use this tool to generate a configuration-cache compatible key:
openssl rand -base64 16
.This should help reduce the configuration phase for all the main worflow tasks in CI.