Skip to content

Restore the Maven cache without saving it in partial-build CI jobs - #9845

Open
sampokuokkanen wants to merge 1 commit into
jruby:masterfrom
sampokuokkanen:ci-restore-only-maven-cache
Open

sampokuokkanen wants to merge 1 commit into
jruby:masterfrom
sampokuokkanen:ci-restore-only-maven-cache

Conversation

@sampokuokkanen

Copy link
Copy Markdown
Contributor

setup-java saves the shared Maven cache from whichever job finishes first. Dependency check won that race on master, and it never runs clean, so the cache has no maven-clean-plugin. Every other job then downloads that plugin from Central on every run and fails whenever Central answers 404.

Dependency check and Verify build artifacts now only restore the cache, so a full build job saves it.

The current bad cache can be deleted with
gh cache delete setup-java-Linux-x64-maven-96f87e209d086aa41312112416ba45ea8ca392352d2145ddef9b3c25e491ce13 -R jruby/jruby

setup-java saves the shared Maven cache from whichever job finishes
first. Dependency check won that race on master, and it never runs
clean, so the cache has no maven-clean-plugin. Every other job then
downloads that plugin from Central on every run and fails whenever
Central answers 404.

Dependency check and Verify build artifacts now only restore the cache,
so a full build job saves it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant