HDDS-10470. Populate Maven dependency cache in separate workflow #6340
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 changes were proposed in this pull request?
Create a separate CI workflow to populate the cache for Maven dependencies from scratch. This prevents cache inflation that can happen if existing cache is updated with new dependencies: obsolete dependencies are never removed.
The workflow runs on
master
andozone-1.4
branches wheneverpom.xml
files are changed. It also runs on a schedule to avoid cache miss due to expiry.Existing workflows are updated to only restore the cache, do not create/update it.
https://issues.apache.org/jira/browse/HDDS-10470
How was this patch tested?
Tested in fork: