The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

SSH key is not working

Ishaan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 8, 2021

I have two private repos and I am using one repo as a library.

I configured for ssh key for one and add it's public key to another's access key.

I am using npm to install another repo as a library.

It works well locally but not working on the main repo's bitbucket pipeline.

Following one is the my example in package.json

"private-module": "git+ssh://git@bitbucket.org/[owner]/[repo]git#0.2.0",

Would you please help me?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 21, 2021

Hi @hiroshi

Welcome to the community.

You mentioned that you configured an SSH key and added the public key to another repository as an Access key.
For this, when you run it on Pipelines, would it be possible for you to confirm if you also added the configured public SSH key on Pipelines?

  1. Go to your repository https://bitbucket.org/workspace_id/repo_name/
  2. Click Repository settings
  3. Click SSH keys

If not yet, would you be able to add it there using the above steps and run your Pipelines build again?

Let me know how it goes.

Regards,
Mark C

TAGS
AUG Leaders

Atlassian Community Events