[
https://issues.apache.org/jira/browse/FLINK-16411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071028#comment-17071028
]
Robert Metzger commented on FLINK-16411:
----------------------------------------
Yes, its very easy to set up a maven cache. I've considered this option as well.
The google guys mentioned there were were some issues (but I don't believe that
this was the cause. We had more cases of the issue today).
Using Azure caching is very reliable, but it adds another 10 minutes of build
time per job (it is only downloading 2GBs of artifacts, but there are quite
some retries). These retries are another indicator for the problem being our
machines / connectivity.
> Maven central connection timeouts on Azure Pipelines
> ----------------------------------------------------
>
> Key: FLINK-16411
> URL: https://issues.apache.org/jira/browse/FLINK-16411
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Some test stages invoke maven again, where additional dependencies are
> downloaded, sometimes failing the build.
> This ticket is about using the Google mirror wherever possible.
> Examples of failing tests:
> -
> https://dev.azure.com/rmetzger/Flink/_build/results?buildId=5882&view=logs&j=636f54dd-dda5-5b4b-f495-2d92ec493b6c&t=6c30efdf-a92a-5da3-9a6a-004c8552b2df
> A failure looks like this:
> {code}
> [ERROR] Failed to execute goal on project flink-hadoop-fs: Could not resolve
> dependencies for project org.apache.flink:flink-hadoop-fs:jar:1.11-SNAPSHOT:
> Could not transfer artifact
> org.apache.flink:flink-shaded-hadoop-2:jar:2.8.3-10.0 from/to central
> (https://repo.maven.apache.org/maven2): GET request of:
> org/apache/flink/flink-shaded-hadoop-2/2.8.3-10.0/flink-shaded-hadoop-2-2.8.3-10.0.jar
> from central failed: Connection reset -> [Help 1]
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
