Repository navigation
Save caches only from the default branch and .x lines - #456
Merged
Merged
Conversation
Every push saved the Maven cache and, through setup-java 6's default, each installed JDK into its own branch scope, where no other build reads it.
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
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 IT workflow saved its caches from every push, including Dependabot and topic branches, and since v6
setup-javaalso cached each JDK it installs. Builds now save only from pushes to the default branch and.xlines, restore read-only elsewhere, and do not cache JDKs. Same change as #454 onmaven-3.10.x.