Changed SSH Key for GIT Repos - Unable to detect changes

Jason Baron December 10, 2015

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 votes
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 10, 2015

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
TAGS
AUG Leaders

Atlassian Community Events