Hi! I'm trying to use the BitBucket Pipelines NPM publish-pipe to publish our NPM package to a NPM repository hosted on Nexus. The URL for our Nexus repository is
https://sample.url/repository/our-package
When the NPM publish pipe runs, it sets the auth-token in the following way:
npm_host=$(node -p "require('url').parse('$npm_registry_url').host")
npm config set //${npm_host}/:_authToken "${NPM_TOKEN}"
The result of this is:
//sample.url/:_authToken=<token>
In other words, since the npm_host only gets the host part (sample.url) of the registry url, the "/repository/" part of our URL is skipped, and the publish returns a 502 error code.
Should maybe the pipe take longer repository URLs into account?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.