Enable Maven cache management for Github Actions #10492
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
- Create a common cache to draw from when no branch caches exist - Rejuvenate the common cache to ensure it's around using pushes, schedule or manual runs - To save space, we automatically trigger a job on a closed PR to delete any caches for the feature branch just merged
"Deplete" seems harder to understand than just plain ol' "delete". Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
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.
What this PR does / why we need it:
This PR is necessary to be merged before we resolve the issue #10428, as we cannot test the functionality without the cache from the default branch being present. This is due to the scoped nature of caches on Github to ensure cache isolation. We cannot create a cache with the default branch scope from a feature branch.
Which issue(s) this PR closes:
Relates to #10428, but does not close it yet.
Special notes for your reviewer:
None
Suggestions on how to test this:
None (another PR forthcoming to actually test if this works)
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Nope
Is there a release notes update needed for this change?:
Nope
Additional documentation:
None