[
https://issues.apache.org/jira/browse/METRON-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856024#comment-16856024
]
Michael Miklavcic commented on METRON-2155:
-------------------------------------------
[~nickwallen] I'm unclear whether #1 will help considering the nature of the
failures I've seen - doesn't even appear to be a problem with the download, the
Travis process just goes AWOL and eventually bombs out with a timeout. Even so,
it might alleviate our problem if there's an issue with how the download
mirrors are accessed in Travis by internalizing the endpoint that we download
from. It won't do anything to address performance, as you mentioned the Travis
docs clearly state - "Large files that are quick to install but slow to
download do not benefit from caching, as they take as long to download from the
cache as from the original source" - but it *may* help with stability. I'd be
in favor of trying this approach first.
#3 - it looks like that Maven wrapper effectively does what we're doing with
curl and unzip -
[https://github.com/takari/maven-wrapper/blob/master/src/main/java/org/apache/maven/wrapper/Installer.java].
If curl is running into issues, this doesn't seem, on the surface, like it's
going to add much value to addressing that problem.
> 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)
