GitHub user bzz opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/808

    ZEPPELIN-776: force CI to always use container-based infra

    ### What is this PR for?
    It forces travis CI to use container-based infra for everything, not only 
`master`.
    
    It will result in [many 
benefits](https://docs.travis-ci.com/user/migrating-from-legacy/#Why-migrate-to-container-based-infrastructure%3F),
 improving CI stability and including reducing [obscure CI failures \w old 
Spark 
versions](https://issues.apache.org/jira/browse/ZEPPELIN-776?focusedCommentId=15219388&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15219388)
    
    ### What type of PR is it?
    Improvement
    
    
    ### What is the Jira issue?
    [ZEPPELIN-776](https://issues.apache.org/jira/browse/ZEPPELIN-776)
    
    ### How should this be tested?
    CI should be green, that is all.
    
    
    ### 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/bzz/incubator-zeppelin 
ZEPPELIN-776-force-ci-to-container-infra

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

    https://github.com/apache/incubator-zeppelin/pull/808.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 #808
    
----
commit d56ed0d51f7206a585b5d93d6729960bf88c44ff
Author: Alexander Bezzubov <b...@apache.org>
Date:   2016-03-31T14:43:14Z

    ZEPPELIN-776: force CI to always use container-based infra

----


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

Reply via email to