[
https://issues.apache.org/jira/browse/METRON-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855793#comment-16855793
]
Nick Allen commented on METRON-2155:
------------------------------------
(1) One way would be to cache the Maven zip file. Travis says this won't help
performance, but at least it might help with the build failures.
[https://docs.travis-ci.com/user/caching/#things-not-to-cache]
(2) Another way would be to cache the directory containing the unzipped maven
binaries. But how does Travis know not to re-download the Maven binary in that
case?
(3) Would using something like mvnw help?
[https://github.com/takari/maven-wrapper] This would make Maven installation
simpler for both users and Travis. I am not sure if this would help the
current build failures that we are seeing though.
> Cache Maven in Travis CI Builds
> -------------------------------
>
> Key: METRON-2155
> URL: https://issues.apache.org/jira/browse/METRON-2155
> Project: Metron
> Issue Type: Bug
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> In the Travis CI builds, we download Maven and even retry up to 10 times
> should this download fail. We continue to see some failures when downloading
> Maven.
> [https://api.travis-ci.org/v3/job/540955869/log.txt]
>
> This could be a problem within Travis' internal networks or this could be an
> intermittent issue with the Apache mirrors. We have no way of knowing and no
> good way to resolve these sorts of problems.
> We could cache the Maven dependency to mitigate this problem. It would not
> truly resolve the problem, but should help mitigate it.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
