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/03/01 02:27:05 UTC

[GitHub] zeppelin pull request #2082: [ZEPPELIN-2123] [branch-0.7] backport travis_ch...

GitHub user Leemoonsoo opened a pull request:

    https://github.com/apache/zeppelin/pull/2082

    [ZEPPELIN-2123] [branch-0.7] backport travis_check.py to branch-0.7

    ### What is this PR for?
    ZEPPELIN-2123 introduces travis_check.py to scale out CI capacity.
    However travis_check.py does not exists in branch-0.7, and PR to branch-0.7 marked as a green without regardless of the actual build result.
    
    Since we're planning to make more releases from branch-0.7 and target branch of some PRs are branch-0.7, i think we need travis_check.py on branch-0.7, too.
    
    ### What type of PR is it?
    Feature
    
    ### Todos
    * [x] - bring travis_check.py to branch-0.7
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2123
    
    ### How should this be tested?
    Check Jenkins successfully read build status from travis for PR targeting branch-0.7.  (this PR)
    
    ### 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 branch-0.7_travis_check_backport

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2082.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 #2082
    
----
commit b4e9def01935eccf3163f238bfafc43a84aa355a
Author: Lee moon soo <mo...@apache.org>
Date:   2017-03-01T00:50:21Z

    add travis_check.py script to branch-0.7

----


---
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 #2082: [ZEPPELIN-2123] [branch-0.7] backport travis_check.py ...

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/2082
  
    @jongyoul Okay, i cherry-picked related commits instead of making new commit.


---
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 #2082: [ZEPPELIN-2123] [branch-0.7] backport travis_check.py ...

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/2082
  
    Merge to branch-0.7 if no further comment


---
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 #2082: [ZEPPELIN-2123] [branch-0.7] backport travis_check.py ...

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/2082
  
    Is there any issue whit cherry-pick it into branch-0.7 from 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.
---

[GitHub] zeppelin issue #2082: [ZEPPELIN-2123] [branch-0.7] backport travis_check.py ...

Posted by jongyoul <gi...@git.apache.org>.
Github user jongyoul commented on the issue:

    https://github.com/apache/zeppelin/pull/2082
  
    It looks like more simple way to handle it :-)


---
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 #2082: [ZEPPELIN-2123] [branch-0.7] backport travis_ch...

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo closed the pull request at:

    https://github.com/apache/zeppelin/pull/2082


---
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.
---