Set the registry for node in prereqs - #2037
Merged
Merged
Conversation
Contributor
|
👍 |
Contributor
|
looks good. |
wedaly
pushed a commit
that referenced
this pull request
Dec 24, 2013
Set the registry for node in prereqs
shimulch
pushed a commit
to open-craft/openedx-platform
that referenced
this pull request
Jan 26, 2021
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
3 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.
I believe the recent build failures in Jenkins are caused by trying to install Node modules via HTTPS through a proxy.
http://stackoverflow.com/questions/11773509/npm-behind-a-proxy-fails-with-status-403
This change sets the npm registry to use HTTP. I've verified that this change resolves the issue on the Jenkins worker box.
@jzoldak @feanil