[jira] [Issue Comment Deleted] (STORM-704) Apply Travis CI

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

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

Jungtaek Lim updated STORM-704:
-------------------------------
    Comment: was deleted

(was: It's first success build of Apache Storm from Travis CI. [https://travis-ci.org/HeartSaVioR/storm/jobs/54201436]

Btw, as I described it earlier, if storm-core is broken we cannot see what tests fail. (It just prints 'clojure failed'.)
If we resolve it everything should be OK.)

> Apply Travis CI
> ---------------
>
>                 Key: STORM-704
>                 URL: https://issues.apache.org/jira/browse/STORM-704
>             Project: Apache Storm
>          Issue Type: Improvement
>         Environment: Travis CI
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>            Priority: Minor
>
> Now Apache Storm takes advantage of Github, we can apply Travis CI to some more advantages.
> - Build matrix
> -- Travis CI supports various JDK versions (openjdk6, openjdk7, oraclejdk7, oraclejdk8), and it can be tested separately.
> - Build automatically
> -- pushed new commits, any new PRs
> - Integrated with Github
> -- Contributors can see his/her PR breaks compilation / test in some minutes.
> -- If he/she adds commits to PR, Travis builds it automatically and update build result.
> Please see [https://travis-ci.org/xetorthio/jedis] for example.
> There're some hurdles applying Travis CI to Apache Storm project, but we can overcome these and finally get great CI.
> Current hurdles
> - asfgit should manage Travis CI setup for the first time
> -- other Apache projects already did it by requesting it to INFRA
> --- ex. [https://issues.apache.org/jira/browse/INFRA-6161]
> - Travis CI restricts stdout with 4M which is too small for Storm maven output.
> -- alternative way : filter Storm's INFO message by {code}mvn clean test -U | egrep -v "[0-9]+ \[.+\] INFO"{code} 
> --- inspired by [https://github.com/apache/tajo/pull/8]
> - In storm-core, we can't see tests failure information on stdout cause it just prints 'clojure failed'.
> -- We need to find a way to upload surefire / clojure tests report files to somewhere, and uploaded files should be visible easily.
> --- Travis supports uploading artifacts to S3 by [https://github.com/travis-ci/artifacts], but S3 is not free.
> -- I'm not familiar with Clojure, but can we print tests summary with clojure tests as same as Java junit tests?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)