[
https://issues.apache.org/jira/browse/STORM-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382790#comment-14382790
]
ASF GitHub Bot commented on STORM-704:
--------------------------------------
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/486
STORM-704 Apply Travis CI to Apache Storm Project
* support build matrix (openjdk6, openjdk7, oraclejdk7, oraclejdk8)
* change log level to WARN while running unit tests
* print out clojure test reports (only errors)
Sure we should ask Apache Infra to set up Travis CI (with asfgit account),
which is not an issue cause many projects on Apache already uses Travis CI.
ex. https://issues.apache.org/jira/browse/INFRA-6161
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HeartSaVioR/storm travis
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/486.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #486
----
commit db813c7781c4359229ddee58bbe40dc763ec0eab
Author: Jungtaek Lim <[email protected]>
Date: 2015-03-26T22:00:35Z
STORM-704 Apply Travis CI to Apache Storm Project
* support build matrix (openjdk6, openjdk7, oraclejdk7, oraclejdk8)
* change log level to WARN while running unit tests
* print out clojure test reports (only errors)
----
> 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.
> -- Change log level in tests to WARN
> - 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)
