[
https://issues.apache.org/jira/browse/FLINK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083685#comment-16083685
]
ASF GitHub Bot commented on FLINK-7141:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/4293
Given that enabling the cache doesn't appear to improve build times I
wouldn't enable it, especially since it does require more efforts for cleaning
up corrupted caches. It appears there are only downsides for us to enabling it.
If we don't cache artifacts across job we don't have to worry about fixing
corrupted artifacts, so that problem would be "solved".
The check is still useful though.
> 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)
