ZEPPELIN-776: force CI to always use container-based infra#808
Closed
bzz wants to merge 2 commits intoapache:masterfrom
Closed
ZEPPELIN-776: force CI to always use container-based infra#808bzz wants to merge 2 commits intoapache:masterfrom
bzz wants to merge 2 commits intoapache:masterfrom
Conversation
bzz
force-pushed
the
ZEPPELIN-776-force-ci-to-container-infra
branch
from
739e92f to
0e550f6
Compare
Member
Author
|
ready to be merged |
Member
|
LGTM |
onkarshedge
pushed a commit
to onkarshedge/incubator-zeppelin
that referenced
this pull request
May 11, 2016
### 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, Hotfix for apache#208 ### 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 Author: Alexander Bezzubov <[email protected]> Closes apache#808 from bzz/ZEPPELIN-776-force-ci-to-container-infra and squashes the following commits: 0e550f6 [Alexander Bezzubov] Remove obsolete notifications hook d56ed0d [Alexander Bezzubov] ZEPPELIN-776: force CI to always use container-based infra
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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, improving CI stability and including reducing obscure CI failures \w old Spark versions
What type of PR is it?
Improvement, Hotfix for #208
What is the Jira issue?
ZEPPELIN-776
How should this be tested?
CI should be green, that is all.
Questions: