[ https://issues.apache.org/jira/browse/FLINK-40406 ]
Martijn Visser deleted comment on FLINK-40406:
----------------------------------------
was (Author: martijnvisser):
Reopening, the job in the description died on maven-wrapper.jar, and that
download is still not covered. 46eb63f0bc2 put the Maven distribution into the
CI image, but every test job still fetches the wrapper jar itself. Five jobs
since the fix, on three branches:
https://github.com/apache/flink/actions/runs/37716701006/job/113119008774
(master nightly 2026-10-08, AdaptiveScheduler misc)
https://github.com/apache/flink/actions/runs/38195297880/job/114640145627
(master nightly 2026-10-12, AdaptiveScheduler e2e group 2)
https://github.com/apache/flink/actions/runs/38299469597/job/114995175394
(release-2.2 push 2026-10-12, python)
https://github.com/apache/flink/actions/runs/38299474530/job/115005936682
(release-2.3 push 2026-10-13, misc)
https://github.com/apache/flink/actions/runs/38993321281/job/117289841829
(release-2.3 nightly 2026-10-17, Java 21 e2e group 1)
{code}
Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper might be
compromised.
Investigate or delete /root/flink/.mvn/wrapper/maven-wrapper.jar to attempt a
clean download.
If you updated your Maven version, you need to update the specified
wrapperSha256Sum property.
Process exited with EXIT CODE: 1.
{code}
> CI: Maven build has no retry on transient Central failures, causing spurious
> PR failures
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-40406
> URL: https://issues.apache.org/jira/browse/FLINK-40406
> Project: Flink
> Issue Type: Improvement
> Components: Build System / CI, Kubernetes Operator
> Reporter: Purushottam Sinha
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.2, 1.20.6, 2.3.1, 2.4.0
>
>
> Problem
> CI jobs fail outright on a single transient error from Maven Central (e.g.
> 502 Bad Gateway), with no retry, causing PRs to show a wall of
> failed/cancelled checks for an infrastructure blip unrelated to the change
> under review.
> example of failure
> https://github.com/apache/flink/actions/runs/35172901228/job/105054722871
> One of the way to fix: add extra retries however it will not help in case of
> 429 error (error limiter)
> Another option: put predownloaded maven to docker image
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
