Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217736741
Thank you for review, @srowen .
I'm not sure the root cause of that. According to the github log, it was
created, [disabled
(HOTFIX)](https://github.com/apache/spark/commit/6ad31e79bfe4fc1d03bd8eb4472b8bd448ee3daf)
by @rxin ,
[re-enabled](https://github.com/apache/spark/commit/591c88c9e2a6c2e2ca84f1b66c635f198a16d112)
by @rxin and
[reverted](https://github.com/apache/spark/commit/4bcea1b8595424678aa6c92d66ba08c92e0fefe5)
by @zsxwing historically. I've heard that from @andrewor14 that it was
resource intensive, too.
Anyway, two weeks ago, when I tried to re-enable that according to @rxin 's
request during in the following PR, there was a functional problem on java
linter on AMP clusters.
[[SPARK-14868][BUILD] Enable NewLineAtEofChecker in checkstyle and fix
lint-java errors](https://github.com/apache/spark/pull/12632)
So, I fixed that in the following PR. Now I think that Java Linter works
now in AMP cluster without any problems.
[[SPARK-14867][BUILD] Remove `--force` option in
`build/mvn`](https://github.com/apache/spark/pull/12631)
However, in this PR, I propose to use Travis CI more actively for simple
code analysis and compilation for the following main reasons. (I know that
Spark uses Travis CI historically and Travis CI cannot supports Spark full
testing.)
- It's free.
- Most GitHub community developers are more familiar with it than AMP
clusters.
- It will reduce the number of PR.
- If we have `.travis.yml`, all the developers own forks have that. It
means they will see the Travis CI result on their branches while making their
PRs, **not Spark PR list.**
- In the future, there is possibility to reduce the workload on AMP
clusters. It means more faster processing the PR requests.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
