Infra: Install MADlib on non-default schema in Jenkins #207
Conversation
This file contains 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
|
Refer to this link for build results (access rights to CI server needed): |
The Jenkins build that runs for every PR and for every master commit is great. Installing MADlib on a non-default schema name such as `mad` would help us identify many issues early (issues that correspond to hard-coding `madlib` in the code/tests). Closes apache#207
njayaram2
force-pushed
the
infra/jenkins_non_default_schema
branch
from
5364ed5
to
627cbb7
Compare
|
Jenkins ok to test |
|
Refer to this link for build results (access rights to CI server needed): |
kaknikhil
pushed a commit
to kaknikhil/madlib
that referenced
this pull request
Jan 12, 2018
Install MADlib on schema `mad` instead of default schema `madlib` for the Jenkins PR and Master CI builds. This would help us identify issues that correspond to hard-coding `madlib` in the code/tests. Closes apache#207
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Jenkins build that runs for every PR and for every master
commit is great. Installing MADlib on a non-default schema name
such as
madwould help us identify many issues early (issuesthat correspond to hard-coding
madlibin the code/tests).PS: The Jenkins build for this PR is expected to fail due to
https://issues.apache.org/jira/browse/MADLIB-1184
Closes #207