[
https://issues.apache.org/jira/browse/FLINK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080394#comment-16080394
]
ASF GitHub Bot commented on FLINK-7141:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/4293
that's actually hard to know in advance - I had only 3 builds that went
under the limit by chance so I was able to use the cache henceforth in those
three which constantly were below the 49min. This PR's Travis build cannot even
use the cache yet although it is creating one.
I don't know whether we can simulate this by simply adding another commit
on top - by chance I did see something that needs change, so we will see ;)
> 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)
