GitHub user Leemoonsoo reopened a pull request:
https://github.com/apache/zeppelin/pull/3231
[MINOR] Let jenkins print some build summary on failure
### What is this PR for?
Currently actual CI build occurs in individual contributor's travis-ci
account, and apache Jenkins poll the result from travis-ci and print build
status on it's console output, like
```
Build https://travis-ci.org/test/zeppelin/builds/451036679
[1] OK https://travis-ci.org/test/zeppelin/jobs/451036680
[2] Running ... https://travis-ci.org/test/zeppelin/jobs/451036681
[3] Running ... https://travis-ci.org/test/zeppelin/jobs/451036682
[4] Not completed https://travis-ci.org/test/zeppelin/jobs/451036683
[5] Running ... https://travis-ci.org/test/zeppelin/jobs/451036684
[6] Running ... https://travis-ci.org/test/zeppelin/jobs/451036685
[7] Running ... https://travis-ci.org/test/zeppelin/jobs/451036686
[8] Not started https://travis-ci.org/test/zeppelin/jobs/451036687
[9] Not started https://travis-ci.org/test/zeppelin/jobs/451036688
[10] Not started https://travis-ci.org/test/zeppelin/jobs/451036689
[11] Not started https://travis-ci.org/test/zeppelin/jobs/451036690
1 job(s) failed, 9 job(s) running/pending
```
When there're failed job, developer has to open the travis-ci link and
download the log and manually look through to see what was wrong.
This PR make Jenkins not only print build status but also short summary of
failure, so developer quickly identify what went wrong. After this patch,
Jenkins console output will look something like
```
[2018-11-18 09:11:20] Author: test, commit: ee6d89b
[2018-11-18 09:11:20] --------------------------------
[2018-11-18 09:11:25] Get build status ...
Build https://travis-ci.org/test/zeppelin/builds/451036679
[1] OK https://travis-ci.org/test/zeppelin/jobs/451036680
[2] OK https://travis-ci.org/test/zeppelin/jobs/451036681
[3] Error 1 https://travis-ci.org/test/zeppelin/jobs/451036682
Tests run: 38, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
153.857 sec <<< FAILURE! - in org.apache.zeppelin.notebook.NotebookTest
Please check full log at
https://api.travis-ci.org/v3/job/451036682/log.txt
[4] Not completed https://travis-ci.org/test/zeppelin/jobs/451036683
Your build has been stopped.
Please check full log at
https://api.travis-ci.org/v3/job/451036683/log.txt
[5] OK https://travis-ci.org/test/zeppelin/jobs/451036684
[6] Error 1 https://travis-ci.org/test/zeppelin/jobs/451036685
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
14.374 sec <<< FAILURE! - in org.apache.zeppelin.spark.SparkRInterpreterTest
Please check full log at
https://api.travis-ci.org/v3/job/451036685/log.txt
[7] Error 1 https://travis-ci.org/test/zeppelin/jobs/451036686
Tests run: 15, Failures: 15, Errors: 0, Skipped: 0, Time elapsed:
216.32 sec <<< FAILURE! - in
org.apache.zeppelin.interpreter.SparkIntegrationTest
Please check full log at
https://api.travis-ci.org/v3/job/451036686/log.txt
[8] Error 1 https://travis-ci.org/test/zeppelin/jobs/451036687
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
17.021 sec <<< FAILURE! - in org.apache.zeppelin.spark.SparkRInterpreterTest
Please check full log at
https://api.travis-ci.org/v3/job/451036687/log.txt
[9] Error 1 https://travis-ci.org/test/zeppelin/jobs/451036688
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
18.169 sec <<< FAILURE! - in org.apache.zeppelin.spark.SparkRInterpreterTest
Please check full log at
https://api.travis-ci.org/v3/job/451036688/log.txt
[10] OK https://travis-ci.org/test/zeppelin/jobs/451036689
[11] Error 1 https://travis-ci.org/test/zeppelin/jobs/451036690
Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
353.585 sec <<< FAILURE! - in org.apache.zeppelin.livy.LivyInterpreterIT
Please check full log at
https://api.travis-ci.org/v3/job/451036690/log.txt
7 job(s) failed, 0 job(s) running/pending
```
### What type of PR is it?
Improvement
### How should this be tested?
* try script manually against some build
e.g.
```
python ./travis_check.py [github username] [commit hash]
python ./travis_check.py NicolasRouquette ee6d89b
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin ci_summary
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/3231.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 #3231
----
commit 9f42b32269d0e76741e7e4783becff0c2e6f2c9e
Author: Lee moon soo <leemoonsoo@...>
Date: 2018-11-18T00:12:30Z
print build log summary
----
---
