replace burrunan/gradle-cache-action with gradle/gradle-build-action
#821
Conversation
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
The older action, `burrunan/gradle-cache-action`, turns GitHub's freebie storage into a remote Gradle build cache. This causes tons of small requests, and as a result we sometimes get 429 errors or timeouts. When this happens, the best case scenario is that Gradle just treats it as a cache miss and rebuilds something locally. In the worst case, CI just fails. This replacement action is Gradle's own. It automatically handles keys and partitioning of the caches, and still uses build cache instead of `/build`. But, it saves/restores those caches in large chunks instead of making a remote build cache. As a result, the I/O is faster and there are far fewer requests.
rjrjr
approved these changes
Jun 24, 2022
| concurrent : true | ||
| gradle-build-scan-report : false | ||
| gradle-distribution-sha-256-sum-warning : false | ||
| assemble --stacktrace |
Collaborator
There was a problem hiding this comment.
I take it --no-daemon is built in now?
Contributor
Author
There was a problem hiding this comment.
More or less.
https://github.com/gradle/gradle-build-action#stopping-the-gradle-daemon
By default, the action will stop all running Gradle daemons in the post-action step, prior to saving the Gradle User Home state. This allows for any Gradle User Home cleanup to occur, and avoid file-locking issues on Windows.
If caching is unavailable or the cache is in read-only mode, the daemon will not be stopped and will continue running after the job is completed.
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.
The older action,
burrunan/gradle-cache-action, turns GitHub's freebie storage into a remote Gradle build cache. This causes tons of small requests, and as a result we sometimes get 429 errors or timeouts. When this happens, the best case scenario is that Gradle just treats it as a cache miss and rebuilds something locally. In the worst case, CI just fails.This replacement action is Gradle's own. It automatically handles keys and partitioning of the caches, and still uses build cache instead of
/build. But, it saves/restores those caches in large chunks instead of making a remote build cache. As a result, the I/O is faster and there are far fewer requests.