[
https://issues.apache.org/jira/browse/FLINK-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142637#comment-15142637
]
ASF GitHub Bot commented on FLINK-3383:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/1619#discussion_r52591570
--- Diff: .travis.yml ---
@@ -17,9 +17,9 @@ language: java
matrix:
include:
- jdk: "oraclejdk8"
- env: PROFILE="-Dhadoop.version=2.7.1 -Dscala-2.11
-Pinclude-yarn-tests -Dmaven.javadoc.skip=true"
--- End diff --
I think it is bad practice because it lets you get away with broken
JavaDoc. On my machine it saves 2 minutes compilation time but for CI I think
we should keep it.
> 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)
