[
https://issues.apache.org/jira/browse/FLINK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082144#comment-16082144
]
ASF GitHub Bot commented on FLINK-7141:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/4293
Looks like with the cache it is only downloading flink artefacts from
earlier versions for API comparisons (I excluded
`$HOME/.m2/repository/org/apache/flink/` from the cache).
Also, it seems there is no real performance gain from using the cache :( or
at least the influence of the differences in the runtime of the tests is bigger
so that the cache's influence is inconclusive.
With the control over deleting corrupt caches ourselves, we could skip the
.m2 repo cleanup and save another 30s there. In the end, we don't know whether
corrupt repositories were caused by Travis or Maven - the settings in this PR
should fix the former and the repo cleanup the latter. We could thus try
removing the latter once we can delete caches ourselves.
> 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)
