Bump cache action from v1 to v2 #269
Merged
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
aepfli
approved these changes
May 27, 2020
|
Hmmm, out of memory? https://github.com/junit-pioneer/junit-pioneer/pull/269/checks?check_run_id=713531770#step:8:244 @aepfli could you please try to re-run the failed builds? Looks like I don't have the rights to do so. I just wonder if this happens again. |
lets see |
|
Kudos, SonarCloud Quality Gate passed!
|
|
🤷♂️ |
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.
Cache action v2 has been released yesterday. Using the new version has several advantages, such as increased performance and improved cache sizes.
While there is also support for multipe paths, I don't think we can leverage this feature since the Sonar and Gradle caches should be invalidated upon different events.
I hereby agree to the terms of the JUnit Pioneer Contributor License Agreement.