Added workaround for missing Solr and yokozuna artifacts on AWS #739
Conversation
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
…llow these artifacts to be hosted elsewhere, and specified with an environment variable. Example: export ARTIFACT_URL_PREFIX="https://files.tiot.jp/riak" make
|
+1 |
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.
This PR allows one to specify an alternate location for Solr and Yokozuna artifacts via the ARTIFACT_URL_PREFIX environment variable. These artifacts have traditionally been located on AWS, but which are currently not present or accessible, can be provided by other parties.
Example:
export ARTIFACT_URL_PREFIX="https://files.tiot.jp/riak"
make