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

This widget could not be displayed.

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
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published 10 hours ago in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

39 views 0 5
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