You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Leemoonsoo <gi...@git.apache.org> on 2017/02/16 10:24:50 UTC
[GitHub] zeppelin pull request #2026: [ZEPPELIN-2123] Travis build status check scrip...
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/2026
[ZEPPELIN-2123] Travis build status check script
### What is this PR for?
This script is designed to check contributors travis CI build state when pullrequest is created.
### What type of PR is it?
Feature
### Todos
* [x] - check travis build status
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2123
### How should this be tested?
Run script with `python ./travis_check.py [Author] [Branch name] [Commit hash]`.
For example
```
moon$ python ./travis_check.py Leemoonsoo ZEPPELIN-2120 44b9403
[2017-02-16 18:55:43] Author: Leemoonsoo, branch: ZEPPELIN-2120, commit: 44b9403
[2017-02-16 18:55:43] --------------------------------
[2017-02-16 18:55:48] Get build status ...
https://travis-ci.org/Leemoonsoo/zeppelin/builds/202172366
[1] OK
[2] Running ...
[3] Running ...
[4] OK
[5] OK
[6] Running ...
[7] OK
[8] Error 1
[9] Running ...
1 job(s) failed, 4 job(s) running
```
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin ZEPPELIN-2123
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2026.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 #2026
----
commit 7de1c24f020510e9a09be45521134e72005ca61b
Author: Lee moon soo <mo...@apache.org>
Date: 2017-02-16T10:20:09Z
Travis build status check script
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin pull request #2026: [ZEPPELIN-2123] Travis build status check scrip...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2026
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2026: [ZEPPELIN-2123] Travis build status check script
Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2026
Looks nice \U0001f44d
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] zeppelin issue #2026: [ZEPPELIN-2123] Travis build status check script
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2026
Thanks @jongyoul for review. I'm merging it to master.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---