Enable Gradle Configuration Cache on GitHub Actions#923
Merged
Conversation
In #899, the `cache-encryption-key` argument was removed from the `gradle/actions/setup-gradle` action to avoid using secrets. However, this secret is optional: if the value is not provided, the cache won't be read or updated. This means that PRs created from the main repository will take advantage of Gradle's Configuration Cache, while PRs from forks won't.
Code Coverage
Files
|
StaehliJ
approved these changes
Mar 5, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pull request
Description
In #899, the
cache-encryption-keyargument was removed from thegradle/actions/setup-gradleaction to avoid using secrets.However, this secret is optional: if the value is not provided, the cache won't be read or updated.
This means that PRs created from the main repository will take advantage of Gradle's Configuration Cache, while PRs from forks won't.
See the corresponding section of the documentation for more information: https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#saving-configuration-cache-data
Changes made
quality.ymlworkflow to support Configuration Cache.Checklist