Repository navigation
ci: retry the Maven steps on a transient failure - #160
Merged
Merged
Conversation
Maven Central answered 403 for a metadata file and a plugin on 2026-10-27, and wickra-verify's CodeQL job failed on main until it was rerun. Maven's resolver does not retry a 403, so every step that runs Maven now goes through nick-fields/retry, the action the workflows already use for npm, dotnet and the binding install: two attempts, 30 seconds apart, 30 minutes per attempt. nick-fields/retry starts the command with `bash -c`, without the -e a run step gets, so multi-line commands begin with the same `set -e` (and pipefail where the step said `shell: bash`). The Maven Central deploy keeps a single attempt: a retry after a first attempt that timed out while Central went on to publish would only run into Central's duplicate check. The version check in front of it and the package step behind it are retried.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
kingchenc
enabled auto-merge (squash)
October 27, 2026 22:10
kingchenc
disabled auto-merge
October 27, 2026 22:11
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
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.
Summary
Maven Central answered 403 for a metadata file and a plugin on 2026-10-27, and wickra-verify's CodeQL job failed on
mainuntil it was rerun. Maven's resolver does not retry a 403, so only a step-level retry catches it.Every step that runs Maven now goes through
nick-fields/retry, the action the workflows already use for npm, dotnet and the binding install: two attempts, 30 seconds apart, 30 minutes per attempt. That covers the binding tests and examples inci.yml, the Java build incodeql.yml, and inrelease.ymlthe version check before the deploy and the package step after it.nick-fields/retrystarts the command withbash -c, without the-ea run step gets, so multi-line commands begin with the sameset -e(andpipefailwhere the step saidshell: bash).mvncalls, which behave the same under bash; wickra's Java job has run its binding install this way on all three OSes for a while.Checks
actionlintandzizmor --offlineare clean on the changed workflows.