[
https://issues.apache.org/jira/browse/SPARK-15207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-15207.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request 12980
[https://github.com/apache/spark/pull/12980]
> Use Travis CI for Java 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
> Fix For: 2.1.0
>
>
> Currently, Java Linter is disabled in Jenkins tests.
> https://github.com/apache/spark/blob/master/dev/run-tests.py#L554
> However, as of today, Spark has 721 java files with 97362 code (without
> blank/comments). It's about 1/3 of Scala.
> {code}
> --------------------------------------------------------------------------------
> Language files blank comment
> code
> --------------------------------------------------------------------------------
> Scala 2353 62819 124060
> 318747
> Java 721 18617 23314
> 97362
> {code}
> 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.
> - 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: [email protected]
For additional commands, e-mail: [email protected]
