[Chore] Avoid duplicate Maven cache restores - #3
Draft
openroomote-bruno[bot] wants to merge 1 commit into
Draft
openroomote-bruno[bot] wants to merge 1 commit into
openroomote-bruno[bot] wants to merge 1 commit into
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.
What changed
Avoid a second Maven (
~/.m2and~/.gitlibs) cache download when frontend setup has already restored it in the same GitHub Actions job. Backend-only jobs retain their existing restore behavior.Why this change was made
The shared frontend and backend setup actions are invoked sequentially by many test jobs, including the 50-way E2E matrix. Both actions were restoring the same weekly cache key and paths, adding duplicated download and extraction time without changing the prepared environment.
Impact
No product behavior changes. Jobs that run frontend setup before backend setup now perform one less Maven cache restore; this should remove roughly 5-30 seconds of setup from each affected matrix leg, with the largest wall-clock gain on E2E runs and an estimated 4-25 runner minutes avoided across a 50-leg E2E matrix.
git diff --checkpassed locally; YAML lint tooling was not available in the sandbox and should run in CI.