[ 
https://issues.apache.org/jira/browse/WAGON-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Muhammad waqas Hanif updated WAGON-604:
---------------------------------------
    Description: 
When the pipelines are executed in Azure pipelines, we are facing a connection 
timeout error. Can you please prioritize as soon as possible, as it is 
impacting all the pipelines including the production builds.

-------------------------------------------------------
Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
project pace-mulesoft-purchase-order-v1: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: org.apache.maven.surefire:maven-surefire-common:jar:2.19.1, 
org.apache.maven.surefire:surefire-booter:jar:2.19.1, 
org.apache.maven:maven-artifact:jar:2.2.1, 
org.codehaus.plexus:plexus-utils:jar:1.5.15: Could not transfer artifact 
org.apache.maven.surefire:maven-surefire-common:jar:2.19.1 from/to central 
(https://repo.maven.apache.org/maven2): Connection timed out (Read failed) ->

  was:
When the pipelines are executed in Azure pipelines, we are facing a connection 
timeout error. Azure pipelines team claims that connection is closed from Maven 
central repo end. Below is the error message. Have attached the complete log 
zip file for your reference. Can you please prioritize as soon as possible, as 
it is impacting all the pipelines including the production builds.

-------------------------------------------------------
Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
project pace-mulesoft-purchase-order-v1: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: Plugin 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1 or one of its 
dependencies could not be resolved: The following artifacts could not be 
resolved: org.apache.maven.surefire:maven-surefire-common:jar:2.19.1, 
org.apache.maven.surefire:surefire-booter:jar:2.19.1, 
org.apache.maven:maven-artifact:jar:2.2.1, 
org.codehaus.plexus:plexus-utils:jar:1.5.15: Could not transfer artifact 
org.apache.maven.surefire:maven-surefire-common:jar:2.19.1 from/to central 
(https://repo.maven.apache.org/maven2): Connection timed out (Read failed) ->


> Connection Timeout error with Maven repo from Azure Pipelines 
> --------------------------------------------------------------
>
>                 Key: WAGON-604
>                 URL: https://issues.apache.org/jira/browse/WAGON-604
>             Project: Maven Wagon
>          Issue Type: Bug
>         Environment: Dev and test environment 
>            Reporter: Muhammad waqas Hanif
>            Priority: Blocker
>              Labels: AZURE, build
>
> When the pipelines are executed in Azure pipelines, we are facing a 
> connection timeout error. Can you please prioritize as soon as possible, as 
> it is impacting all the pipelines including the production builds.
> -------------------------------------------------------
> Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
> project pace-mulesoft-purchase-order-v1: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: Plugin 
> org.apache.maven.plugins:maven-surefire-plugin:2.19.1 or one of its 
> dependencies could not be resolved: The following artifacts could not be 
> resolved: org.apache.maven.surefire:maven-surefire-common:jar:2.19.1, 
> org.apache.maven.surefire:surefire-booter:jar:2.19.1, 
> org.apache.maven:maven-artifact:jar:2.2.1, 
> org.codehaus.plexus:plexus-utils:jar:1.5.15: Could not transfer artifact 
> org.apache.maven.surefire:maven-surefire-common:jar:2.19.1 from/to central 
> (https://repo.maven.apache.org/maven2): Connection timed out (Read failed) ->



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to