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:
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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.