maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Gent (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MNG-6604) Intermittent failures while downloading GAVs from Nexus
Date Tue, 02 Jul 2019 12:49:00 GMT

    [ https://issues.apache.org/jira/browse/MNG-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876930#comment-16876930
] 

Adam Gent edited comment on MNG-6604 at 7/2/19 12:48 PM:
---------------------------------------------------------

Since this is happening on our build machine and our build machine has file system access
to the repository I'm wondering what would happen if I just use file system access instead
of HTTP wagon. I would imagine it would reduce the race condition but not eliminate it.

EDIT I also like to add that our build machine (jenkins) uses a separate repository per build
so this is fairly annoying given all the separation we are already doing.

I love Maven but this critical problems that don't ever seem to fixed are making me reconsider
Gradle.


was (Author: agentgt):
Since this is happening on our build machine and our build machine has file system access
to the repository I'm wondering what would happen if I just use file system access instead
of HTTP wagon. I would imagine it would reduce the race condition but not eliminate it.

> Intermittent failures while downloading GAVs from Nexus
> -------------------------------------------------------
>
>                 Key: MNG-6604
>                 URL: https://issues.apache.org/jira/browse/MNG-6604
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line, Toolchains
>    Affects Versions: 3.6.0
>         Environment: Nexus OSS 3.15.2-01
> Docker 18.09.2 on Ubuntu 18.04.2 LTS
> Gitlab runner 11.8.0
>            Reporter: Ivan Rizzante
>            Priority: Major
>         Attachments: docker-env.txt, log.txt
>
>
> Hello
> we're running maven 3.6.0 builds in a docker container and we use Nexus OSS configured
as proxy for Maven Central.
> While running our builds using Gitlab CI, we're experiencing intermittent build failures
because Maven cannot find artifacts in Nexus which we verified they are actually available.
> Error example below:
> {noformat}
> 20744 [main] [ERROR] Failed to execute goal on project EcotransitWSClient: Could not
resolve dependencies for project it.sdb.ecotransit:EcotransitWSClient:jar:7.0.1-SNAPSHOT:
Could not transfer artifact commons-beanutils:commons-beanutils:jar:1.9.3 from/to nexus (http://maven-repo.sdb.it:8081/repository/maven-public/):
/builds/sdb/webportal/.m2/repository/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.jar.part
(No such file or directory) -> [Help 1]
> {noformat}
> I attached the full maven build log and our Docker env settings.
> We tried disabling the keep alive and also disabling the connection pooling but nothing
seems to fix the issue.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message