You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2016/05/08 01:51:12 UTC

[jira] [Created] (SPARK-15207) Use Travis CI for Java/Scala/Python Linter and JDK7/8 compilation test

Dongjoon Hyun created SPARK-15207:
-------------------------------------

             Summary: Use Travis CI for Java/Scala/Python Linter and JDK7/8 compilation test
                 Key: SPARK-15207
                 URL: https://issues.apache.org/jira/browse/SPARK-15207
             Project: Spark
          Issue Type: Task
          Components: Build
            Reporter: Dongjoon Hyun


Currently, Java Linter is disabled due to lack of testing resources.

https://github.com/apache/spark/blob/master/dev/run-tests.py#L554

This issue aims to take advantage of Travis CI to handle the following static analysis by adding a single file, `.travis.yml` without any additional burden on the existing servers.

- Apache License Check
- Python Linter
- Scala Linter
- Java Linter
- JDK7/JDK8 maven compile

Note that this issue does not propose to remove some of the above work items from the Jenkins. It's possible, but we need to observe the Travis CI stability for a while.

The goal of this issue is to removing committer's overhead on linter-related PRs (the original PR and the fixation PR).

By the way, historically, Spark used Travis CI before.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org