flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3383) Separate Maven deployment from CI testing
Date Mon, 07 Mar 2016 17:18:40 GMT

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

ASF GitHub Bot commented on FLINK-3383:

Github user asfgit closed the pull request at:


> Separate Maven deployment from CI testing
> -----------------------------------------
>                 Key: FLINK-3383
>                 URL: https://issues.apache.org/jira/browse/FLINK-3383
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System, Tests
>    Affects Versions: 1.0.0
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Critical
> We currently handle our tests and the deployment of the Maven artifacts via Travis CI.
Travis has a maximum allowed build time of two hours which we reach nearly every time. By
that time, the tests have already been run but the deployment is still undergoing.
> I propose to remove the Maven deployment from Travis. Instead, we could use Apache's
Jenkins service or Apache's Buildbot service to trigger a deployment once a day.  

This message was sent by Atlassian JIRA

View raw message