Merged
Conversation
setup-gradle handles cache
leviem1
approved these changes
Jun 30, 2026
leviem1
left a comment
leviem1
left a comment
Member
There was a problem hiding this comment.
Approved with one RFC. Good to merge as-is though
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.
CHANGED - Removed duplicate Gradle cache configuration
CHANGED - Replaced verbose Gradle logging with stack traces on failure
CHANGED - Upload build artifacts only from Ubuntu jobs
CHANGED - Upload test reports only when builds fail
CHANGED - Added artifact retention periods and missing-file handling
CHANGED - Removed unnecessary write permissions from build jobs
CHANGED - Clarified the common setup action description
Should address the Windows issue caused by competing Gradle caches.