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

["Maximilian Michels (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maximilian Michels closed FLINK-3383.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0

Fixed in c413b23b8c8dd3323d4a3d82feed0abab2b339a0.

> 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
>             Fix For: 1.1.0
>
>
> 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)