I have a build set up for a Node.js module that has a step which executes 'npm install'. The package.json file, which specifies the module's dependencies includes at least one private git repo:
+ "module-name": "git+ssh://email@example.com:OurOrgName/module-name.git#v0.0.1",
This is a standard practice in Node.js. You can see the docs for doing so here: https://npmjs.org/doc/json.html (search for "git+ssh").
We're using a deploy key to clone our repo from github initially, which works fine. The next step is our npm install step, which itself attempts to git clone the private repos similar to what's shown above. These fail with an authentication error. Since deploy keys are 1:1 between Bamboo and a repo, it doesn't seem to make sense to use them in this scenario.
How should I be setting up my Node.js project so that it can run npm install and git clone any private repos that I have specified in its package.json file?
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events