Jenkinsfile / Docker : pointing to a “npm” private registry
I'm using a Jenkinsfile to build and publish node packages.
After the usual checkout step, I use the following code to install my components.
node {
docker.image('node').inside {
sh 'npm install'
}
}
It works fine with the default registry (https://registry.npmjs.org). But if a package contains a .npmrc file pointing to a private registry (reachable through a browser) then it fails.
How can I point to a private register through the docker container generated by the Jenkinsfile ?
Thanks a lot :)
node.js docker jenkins npm jenkins-pipeline
add a comment |
I'm using a Jenkinsfile to build and publish node packages.
After the usual checkout step, I use the following code to install my components.
node {
docker.image('node').inside {
sh 'npm install'
}
}
It works fine with the default registry (https://registry.npmjs.org). But if a package contains a .npmrc file pointing to a private registry (reachable through a browser) then it fails.
How can I point to a private register through the docker container generated by the Jenkinsfile ?
Thanks a lot :)
node.js docker jenkins npm jenkins-pipeline
If the private registry need proxy to access, you need add proxy settings in.npmrc. If it needs user/[password to access, you also need to config auth for that.
– yong
Jan 2 at 6:27
add a comment |
I'm using a Jenkinsfile to build and publish node packages.
After the usual checkout step, I use the following code to install my components.
node {
docker.image('node').inside {
sh 'npm install'
}
}
It works fine with the default registry (https://registry.npmjs.org). But if a package contains a .npmrc file pointing to a private registry (reachable through a browser) then it fails.
How can I point to a private register through the docker container generated by the Jenkinsfile ?
Thanks a lot :)
node.js docker jenkins npm jenkins-pipeline
I'm using a Jenkinsfile to build and publish node packages.
After the usual checkout step, I use the following code to install my components.
node {
docker.image('node').inside {
sh 'npm install'
}
}
It works fine with the default registry (https://registry.npmjs.org). But if a package contains a .npmrc file pointing to a private registry (reachable through a browser) then it fails.
How can I point to a private register through the docker container generated by the Jenkinsfile ?
Thanks a lot :)
node.js docker jenkins npm jenkins-pipeline
node.js docker jenkins npm jenkins-pipeline
asked Jan 1 at 21:27
EolEol
1
1
If the private registry need proxy to access, you need add proxy settings in.npmrc. If it needs user/[password to access, you also need to config auth for that.
– yong
Jan 2 at 6:27
add a comment |
If the private registry need proxy to access, you need add proxy settings in.npmrc. If it needs user/[password to access, you also need to config auth for that.
– yong
Jan 2 at 6:27
If the private registry need proxy to access, you need add proxy settings in
.npmrc. If it needs user/[password to access, you also need to config auth for that.– yong
Jan 2 at 6:27
If the private registry need proxy to access, you need add proxy settings in
.npmrc. If it needs user/[password to access, you also need to config auth for that.– yong
Jan 2 at 6:27
add a comment |
1 Answer
1
active
oldest
votes
Solution here: https://docs.npmjs.com/docker-and-private-modules
Basically, you need to configure your npm environment to be able to call the private registry before npm install. On your machine you would do something like npm login which is interactive and not suited for docker builds!
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999067%2fjenkinsfile-docker-pointing-to-a-npm-private-registry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solution here: https://docs.npmjs.com/docker-and-private-modules
Basically, you need to configure your npm environment to be able to call the private registry before npm install. On your machine you would do something like npm login which is interactive and not suited for docker builds!
add a comment |
Solution here: https://docs.npmjs.com/docker-and-private-modules
Basically, you need to configure your npm environment to be able to call the private registry before npm install. On your machine you would do something like npm login which is interactive and not suited for docker builds!
add a comment |
Solution here: https://docs.npmjs.com/docker-and-private-modules
Basically, you need to configure your npm environment to be able to call the private registry before npm install. On your machine you would do something like npm login which is interactive and not suited for docker builds!
Solution here: https://docs.npmjs.com/docker-and-private-modules
Basically, you need to configure your npm environment to be able to call the private registry before npm install. On your machine you would do something like npm login which is interactive and not suited for docker builds!
answered Jan 2 at 6:43
frsechetfrsechet
312312
312312
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53999067%2fjenkinsfile-docker-pointing-to-a-npm-private-registry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If the private registry need proxy to access, you need add proxy settings in
.npmrc. If it needs user/[password to access, you also need to config auth for that.– yong
Jan 2 at 6:27