I have published an npm package to the bitbucket npm package repo using a pipeline. The pipeline auth's using the BITBUCKET_PACKAGES_USERNAME and BITBUCKET_PACKAGES_TOKEN and successfully publishes the npm package to bitbucket packages.
I would now like to install the published package as part of a build step in a bitbucket pipeline of another repo (in the same bitbucket workspace). I have tried to auth using BITBUCKET_PACKAGES_USERNAME and BITBUCKET_PACKAGES_TOKEN variables but the package is not accessible.
How can I give the pipeline access to packages that aren't linked to it's repository?
I think the BITBUCKET_PACKAGES_USERNAME and BITBUCKET_PACKAGES_TOKEN variables are scoped to the repository where the pipeline is running, which is why they cannot access packages published under a different repository.
I would try an alternative type of authentication, like a shareed workspace access token that gives "read" access to all repos.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.