lymerin opened a new pull request, #7781: URL: https://github.com/apache/shenyu/pull/7781
Fixes #7767 **Draft:** I will validate the affected workflows on GitHub-hosted runners on my fork repositories before marking this PR ready for review. ## Problem Maven Central transfer failures abort CI builds without a workflow-level retry. The E2E image-build job also saves the Maven repository cache but does not restore it before building. ## Impact Dependency-download failures stop build jobs and fail their aggregate checks, blocking PRs before the affected validation completes. ## Changes - Add bounded retries for Maven Central connection resets and HTTP 429/502 responses: at most three executions, with 10-second and 20-second delays. - Retry only when all terminal Maven failures are eligible transfer errors. Compilation, test, missing-artifact, and mixed failures remain failures. - Apply the helper to PR builds, integration build/test steps, E2E image/example builds, and the SQL list-contract check. - Restore the Maven repository before E2E image builds using the existing cache key and save mechanism. - Add focused behavior tests and run them in the existing CI changes job. ## Validation - All 20 local shell behavior cases passed. - Classification checks against four original CI logs passed. - Bash syntax checks and ShellCheck passed. - No new actionlint diagnostics compared with the base revision; existing diagnostics remain. ## Non-blocking note Artifact expiration during partial reruns and unrelated test failures are outside this PR’s scope. ## Checklist Make sure that: - [x] You have read the [contribution guidelines](https://shenyu.apache.org/community/contributor-guide). - [x] You submit test cases (unit or integration tests) that back your changes. - [x] Your local test passed `./mvnw clean install -Dmaven.javadoc.skip=true`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
