You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/02/09 18:30:18 UTC

[jira] [Created] (FLINK-3383) Separate Maven deployment from CI testing

Maximilian Michels created FLINK-3383:
-----------------------------------------

             Summary: 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
(v6.3.4#6332)