[
https://issues.apache.org/jira/browse/FLINK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083621#comment-16083621
]
ASF GitHub Bot commented on FLINK-7141:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/4293
sounds like a good plan but in the past it wasn't clear where the caches
got corrupted, i.e. by travis during cache restore, or by mvn during the build.
If the former is still possible, we could only fix it for the next build.
Should I try to introducing this technique?
> enable travis cache again
> -------------------------
>
> Key: FLINK-7141
> URL: https://issues.apache.org/jira/browse/FLINK-7141
> Project: Flink
> Issue Type: Improvement
> Components: Build System, Travis
> Affects Versions: 1.4.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
>
> In the past, we had some troubles with the travis cache but in general it may
> be a good idea to include it again to speed up build times by reducing the
> time the maven downloads take.
> This time, we should also deal with corrupt files in the maven repository and
> [tune
> travis|https://docs.travis-ci.com/user/caching/#Caches-and-build-matrices] so
> that it does not create corrupt caches in the first place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
