Prepare Bamboo Data Center repositories for Bitbucket Cloud SSH hostname change
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Bitbucket Cloud is moving Git over SSH from bitbucket.org to ssh.bitbucket.org. Both hostnames are currently usable; however, 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.
Bamboo repositories that use the old hostname over SSH must be updated to avoid interruptions to connection tests, change detection, and builds. HTTPS repository connections are unaffected. See the Bitbucket Cloud announcement for more specifics and BAM-26574.
Diagnosis
Bamboo Data Center with Git or Bitbucket Cloud repositories that connect to Bitbucket Cloud over SSH.
The repository may be configured at the global, project, or plan level.
The implications depend on the Bamboo repository type used
Repository type | Implications |
Git | Repository URL is editable and defined by user on the repository configuration screen. Can and must be manually migrated. |
Bitbucket Cloud | Repository URL is hardcoded within Bamboo and cannot be edited. Bamboo must be upgraded to a fixed version or you must leverage one of the workarounds below. |
Bamboo uses its SSH proxy for these repository connections. For a Bitbucket Cloud repository, a Git url.insteadOf rule does not change the hostname to which Bamboo's SSH proxy connects.
For plain Git type repositories you can check the SSH URL configured. SSH URL using the old hostname looks like:
git@bitbucket.org:<workspace>/<repo>.git
ssh://git@bitbucket.org/<workspace>/<repo>.gitFor Bitbucket Cloud type repositories, they are affected unless running a fixed version of Bamboo (10.2.24, 12.1.12, 13.0.0)
Before the migration deadline, a connection test can still succeed with the old hostname. After the deadline, SSH operations that continue to connect to bitbucket.org will fail. Affected operations can include repository connection tests, change detection, and source code checkout.
Cause
Bitbucket Cloud is retiring SSH access on bitbucket.org; SSH traffic must connect to ssh.bitbucket.org instead.
Solution
Bitbucket Cloud repository type
Upgrade to a Bamboo version that includes the fix for BAM-26574:
Bamboo 13.0.0
At the time of writing, Bamboo 10.2.24 and 12.1.12 are available.
See Additional checks 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@bitbucket.org:<workspace>/<repo>.git
ssh://git@bitbucket.org/<workspace>/<repo>.gitWorkaround
Bitbucket Cloud repository type
Theoretically, this can also be used for plain Git type repositories, too, if you cannot feasibly edit all the repository URLs manually. 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.orgRestart the Bamboo server and each affected agent after applying the mapping so Bamboo's SSH proxy picks it up.
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.orgon port 22.Script tasks: Review any script tasks that use an explicit repository URL, including the Bamboo variable
bamboo.repository.%.repositoryUrland evaluate how this change might affect the functionality of your script.
Was this helpful?