Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 10 Jul 2017 13:45:00 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.13085898.1499681708000.207220.1499694300345@Atlassian.JIRA>
In-Reply-To: <JIRA.13085898.1499681708000@Atlassian.JIRA>
References: <JIRA.13085898.1499681708000@Atlassian.JIRA> <JIRA.13085898.1499681708372@jira-lw-us.apache.org>
Subject: [jira] [Commented] (FLINK-7141) enable travis cache again
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Jul 2017 14:04:45 -0000


    [ https://issues.apache.org/jira/browse/FLINK-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080342#comment-16080342 ] 

ASF GitHub Bot commented on FLINK-7141:
---------------------------------------

Github user zentol commented on the issue:

    https://github.com/apache/flink/pull/4293
  
    Forks also benefit from this.
    
    It would be cool if we knew how much this affects the build times given that we're also adding more work (for the scanning of the cache).
    
    Note that the travis build for the PR has several builds going over the timeout limit.


> 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)