Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,753
Community Members
 
Community Events
176
Community Groups

I cannot check out submodules using SSH in Windows

Edited

Bamboo is able to talk to my Bitbucket server and clone the main repository using the automatically generated SSH key (shown under "advanced settings")

However, after adding this same public key to the various submodules in bitbucket, and to the top-level project as well, but Bamboo still tells me it does not have permission to access the submodules during checkout.  

I have also tried setting my HOME variable to C:\atlassian\bamboo-home and putting an id_rsa key pair I generated myself into C:\atlassian\bamboo-home\.ssh

I have also tried putting them in various USERPROFILE folders, including the admin user profile which is at C:\Windows\system32\config

I have also tried explicity pointing GIT_SSH_COMMAND to "ssh -i C:\atlassian\bamboo-home\.ssh\id_rsa"

Nothing works.

The only thing that works for me is to check out the submodules using a separate script task that runs after the main repository checkout is complete. In this script, I explicitly load my own keys using OpenSSH.

Where does Bamboo get its SSH keys for submodule checkout?  Why isn't it using the same key it used for the main repository?

```

19-Apr-2019 18:53:50git@bitbucket.<mycompany>.com: Permission denied (publickey).
19-Apr-2019 18:53:50fatal: Could not read from remote repository.
19-Apr-2019 18:53:50 
19-Apr-2019 18:53:50Please make sure you have the correct access rights
19-Apr-2019 18:53:50and the repository exists.

 

1 answer

0 votes

Hello @Jack Zylkin :)

Bamboo uses a proxy internally to handle Git repositories. In your case, you seem to be getting troubles with the submodules authentication coming from the same Bitbucket server, correct?

If that's is true, do you have the submodules repositories configured with absolute url? Could you try with relative urls?

Did that help you?

Victor

I do have them configured with absolute URLs.  I did not realize you could make them relative.

And yes it is the same server.  I would really prefer not to use relative submodule paths, but I can try it.

Did you have a chance to try @Jack Zylkin ? Did it succeed?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events