MINOR: Stabilize Maven cache key#11
Draft
xborder wants to merge 1 commit into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 removes
**/*.javafrom the Docker volume cache key used by the Linux test matrix.The cached Docker volume contains Maven dependencies and plugins under
~/.m2, which change whenpom.xmlfiles or the compose setup changes, not when Java source files change. Keeping Java sources in the key makes Java-only PRs miss the primary cache and then upload a fresh large cache.The key now hashes only
compose.yamland**/pom.xml, while keeping the same restore prefix. Dependency changes still produce a new cache key, but Java-only PRs can reuse the existing Maven dependency cache.Validation: the Test workflow passed. Compared with control PR #7, this first run is mostly a cache-seeding run, so Linux timings are similar. The cache logs show the new stable JDK/Maven key was saved once, and parallel jobs using the same key skipped saving because another job had already created it.