You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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"
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:50||git@bitbucket.<mycompany>.com: Permission denied (publickey).|
|19-Apr-2019 18:53:50||fatal: Could not read from remote repository.|
|19-Apr-2019 18:53:50||Please make sure you have the correct access rights|
|19-Apr-2019 18:53:50||and the repository exists.|
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?