maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6465) Artifact download failures
Date Fri, 24 Aug 2018 12:20:00 GMT

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

Robert Scholte commented on MNG-6465:
-------------------------------------

It is onclear what you mean by "machines" and if you have enough control.
First thing that comes to my mind: consider using a [repository manager|https://maven.apache.org/repository-management.html],
which makes it much easier to control these kind of settings.
If machine is a build server, try adding the following option by default:  {{-C,--strict-checksums
                 Fail the build if checksums don't match}}
This will at least fail the build fast.


> Artifact download failures
> --------------------------
>
>                 Key: MNG-6465
>                 URL: https://issues.apache.org/jira/browse/MNG-6465
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.5.0
>         Environment: Windows, Ubuntu
>            Reporter: Lasse Westh-Nielsen
>            Priority: Major
>
> Hey,
> We often run Maven builds of [https://github.com/neo4j/neo4j] on machines with cold
caches/ empty ~/.m2/repository folders.
> There are rather a lot of dependencies to download, so even though the failure rate of
individual artifact downloads is small, at our scale it causes significant build failures.
> I am working on seeding caches. Separately though it would be great to be able to configure
retries and timeouts for dependency downloads - optimise for build throughput rather than
latency as it were.
> How do I do that? I can't find it documented anywhere, and trying to browse "wagon" source
code got me nowhere.
> Regards,
> Lasse
>  



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

Mime
View raw message