[FLINK-3383] Separate Maven deployment from CI testing

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: Build System, Tests
• Assignee: Maximilian Michels
• Reporter: Maximilian Michels
• Created: 09/Feb/16 17:29
• Updated: 07/Mar/16 17:19
• Resolved: 07/Mar/16 17:19

Description

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.