Use setup-gradle to setup cache when building android apps #138
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
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.
This pulls request contain a fix for the Gradle cache.
Based on previous usage of GitHub Actions, the workflow is unable to download the latest cache uploaded by the previous run. It is noticed that setup-java seems to have limited features when comes to cache. Switching to setup-gradle (first-party actions) should fix the cache loading error. Also, this is also recommended in this issue actions/setup-java#588.
As a side note, this also updates the package-lock.json file. I noticed that you didn't upload the latest package-lock.json causing overhead for the CI to reconfigure the package-lock file every runs.