Set -registry parameter in 'Global npm packages to install' set no_proxy environment variable at Jenkins startup -> it could have other side effect on other Jenkins features.Īdded a comment - 13:11 I agree with you regarding the global installation mainly concern 3rd party tools like bower, gulp, etc.set -registry parameter in 'Global npm packages to install'.I change the priority to Major because to sum up, it involves two workarounds now: The NodeJS plugin should be able to set no_proxy variable to deal with such requested feature. I also try -noproxy or -no_proxy option without any positive result.Īs workaround I set no_proxy environment variable beside JENKINS_HOME in my nf script -> I can access to the internal repo now when Jenkins settings are enabled. I tried to set -no-proxy '' without any success. The problem now if I set Jenkins proxy settings, the 'No proxy' setting is ignored by 'Global Tools Configuration' and I get HTTP 403. It's our case.īut in our company we use a corporate registry to achieve better network performance and avoid external traffic. I agree with you regarding the global installation mainly concern 3rd party tools like bower, gulp, etc.

Npm config set registry default