Changed SSH Key for GIT Repos - Unable to detect changes

We recently had a need to disable an Account/SSH key on our git repo account. This account apparently was tied to our Bamboo Builds. I have updated Bamboo to now use the new SSH key. New builds are working fine but all the old builds are failing and reporting "Unable to detect changes." our work around to fix this is:

  1. Select the build that is erroring
  2. Select Actions
  3. Select Configure Branch
  4. Select the Source Repository Tab
  5. Check Change SSH Key and upload a key file.

This seems to work  but there are many hundreds that are not using the new SSH key. Is there something that we can do do a mass update on the ssh key used on prior builds to fix this issue?

1 answer

0 vote

Hello @J Baron,

Unfortunately there is no automatic way to solve it. Bamboo creates copy of repository for each branch plan. We are aware of this issue and going to address it next year

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,572 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you