Bitbucket Cloud integration support for SSH hostname migration to ssh.bitbucket.org

XMLWordPrintable

      Note

      Please note, the Bamboo fix for this issue does not migrate or alias the hostname for plain Git repositories. That URL is manually editable within your repository configuration and you must migrate it manually)

      This fix only applies to repositories of type Bitbucket Cloud

      Issue Summary

      Bitbucket Cloud is moving Git over SSH from bitbucket.org to ssh.bitbucket.org. Brownouts starting from November 12, 2026 will cause SSH connections to bitbucket.org to be refused during the brownout windows. After December 10, 2026, all SSH connections to bitbucket.org will be refused.

      The impact differs by Bamboo repository type:

      • A plain Git repository has an editable URL.
      • A Bitbucket Cloud repository uses a hardcoded SSH URL, so we cannot change its hostname in the repository configuration. Bamboo’s SSH proxy also means a Git url.insteadOf rule does not redirect that connection.

      Solution

      Bitbucket Cloud repository type

      Upgrade to a Bamboo version that includes the fix:

      At time of writing, Bamboo 10.2.24 and 12.1.12 are available.

      See Additional checks below for further steps that may be required after upgrading, depending on your configuration. 

      Git repository type

      Edit the repository's SSH URL in Bamboo, replacing only the hostname. For example:

      git@ssh.bitbucket.org:<workspace>/<repo>.git
      ssh://git@ssh.bitbucket.org/<workspace>/<repo>.git 

      Workaround

      Bitbucket Cloud repository type

      The SSH URL for this repository type cannot be edited in Bamboo. If you cannot upgrade to a fixed version yet, add the following mapping to ~/.ssh/config for the operating-system account running the Bamboo server and agents:

      Host bitbucket.org
          HostName ssh.bitbucket.org 

      Restart the Bamboo server and each affected agent after applying the mapping so Bamboo's SSH proxy picks it up.

      Theoretically this can also be used for plain Git type repositories too if you cannot feasibly edit all the repository URLs manually.

      Additional checks

      • Trusted keys: If Bamboo's trusted-key management is enabled, verify and approve the SSH host key presented by the new endpoint. See Managing trusted keys in Bamboo.
      • Connection allowlist: If Bamboo's global connection allowlist is enabled, add ssh.bitbucket.org. See Configuring the allowlist. Example Regular Expression: ssh://ssh\.bitbucket\.org/.*
      • Network rules: If outbound SSH is restricted, allow connections to ssh.bitbucket.org on port 22.
      • Script tasks: Review any script tasks that use an explicit repository URL, including the Bamboo variable bamboo.repository.%.repositoryUrl and evaluate how this change might affect the functionality of your script.

              Assignee:
              Mateusz Szmal
              Reporter:
              Jeremy Owen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: