Handling of caching across runs using gradle-build-action
#1960
Conversation
This file contains 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
lhstrh
force-pushed
the
windows-cache
branch
5 times, most recently
from
9d3e8c9
to
9503246
Compare
lhstrh
changed the title
gradle-build-action
axmmisaka
approved these changes
Aug 28, 2023
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
lhstrh
commented
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1898.
The default behavior of this action is to only write the cache on
main/master, but this leads to cache misses and the associated network errors that occur when downloading stuff, so we allow writing to the cache in all branches currently. We should keep and eye on this and make adjustments down the road..