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
Community Members
Community Events
Community Groups

Git submodules using ssh on a remote agent


I am having a problem with my submodules in bamboo. I'm using GIT. This is a Windows machine. I was able to get the submodules to work by adding my ssh key into the bamboo home directory, but I don't know if that same fix is supposed to work with an agent.

Has anyone been successful in cloning submodules using an remote agent?

2 answers

1 accepted

0 votes
Answer accepted

Hi Chris,

I feel you are experiencing the issue reported at The available workaround are two folds:

# Use private key fro the repository that are not protected by passpharase

# Setting up each agent .ssh/config configuration manually to allow Remote Agent machines access your git repository via ssh (using private SSH keyfiles stored on those machines).

Try the options and lets know how it goes for you.



Hi Sultan,

My private keys do not have a passphrase.

As for the second point, I'm not sure where the Bamboo is looking to find the .ssh private key. I have a few on the Remote Agent. Is the path "%USERPROFILE%\.ssh"? Or is Bamboo looking in a different location?



Yes Bamboo is looking at the %USERPROFILE%\.ssh directory

Could you please provide an example of how my config should look like? I set mine up to as


IdentityFile C:\Users\{current user}\.ssh\id_rsa

That is where my private key is located. Although the submodules are still giving me a "permission denied" error.

Here is the error I get:

Warning: Permanently added '[StashURL:7999' (RSA) to the list of known hosts. Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Clone of 'ssh://git@StashURL:7999/sm/windows-common.git' into submodule path 'common' failed)

When I run the command in the command prompt, it clones the repo just fine.

I created a work around. I had a different machine checkout the code and this PC compile it. After a while, I accidentally forgot to set this new machine as a requirement and the checkout of the submodules worked.

Hi Chris,

Thanks alot for the feedback

Did you ever get to the bottom of where to locate the private key on the remote agent? I'm still trying to solve this problem.

You know. I never did, but i did find a solution for myself.

I'm not sure if it was my particular instance or just how bamboo handles submodules, but it kept looking for the ssh key in "$Git_repository/y/.ssh". I ended up just comitting "/y/.ssh/config" into my repository that pointing to the ssh key I wanted to use, then everything worked just fine.

@Sultan Maiyaki but Bamboo is running as service, so where is the %USERPROFILE%\.ssh ? i had tried with /User/Default/.ssh but no luck to make it work.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

304 views 0 7
Read article

Atlassian Community Events