Overview
This guide covers how to add the generated public SSH key as an access key (deploy key) to your Bitbucket repository.Before you start: Create your Git integration first by following the integration form instructions. You’ll need the public SSH key from that integration.
Prerequisites
- Access to Bitbucket Cloud or Bitbucket Server/Data Center
- Admin access to your repository (required to add access keys)
- Public SSH key from your Git integration
⏱️ Estimated time: 5 minutes
IP Whitelisting (If Required)
If your Bitbucket workspace uses IP allowlisting, add the Coalesce Quality egress IP addresses for your region. See IP Whitelist for the complete list. For instructions on configuring IP allowlisting in Bitbucket, see Bitbucket’s guide on IP allowlisting.Adding the Access Key
Repository URL Format
When configuring the integration, use the SSH URL format for Bitbucket: Format:git@bitbucket.org:workspace/repository.git
Example: git@bitbucket.org:mycompany/analytics-platform.git
For Bitbucket Server/Data Center, the format may vary:
git@bitbucket.example.com:project/repository.gitssh://git@bitbucket.example.com:7999/project/repository.git
Troubleshooting
Access key not working
- Verify the complete public key was copied (including the
ssh-rsaorssh-ed25519prefix) - Ensure the access key was added to the correct repository
- Confirm the key has read-only permissions
Connection refused
- Check that your workspace’s IP allowlist (if configured) includes the Coalesce Quality egress IPs
- Verify the repository SSH URL is correct in the integration form
- For Bitbucket Server, ensure the instance is accessible from the Coalesce Quality IP addresses
No Repository Settings visible
- Confirm you have admin access to the repository
- Check with your Bitbucket administrator for access permissions
SSH URL format issues
- Bitbucket Cloud uses:
git@bitbucket.org:workspace/repo.git - Bitbucket Server may use a custom port:
ssh://git@hostname:7999/project/repo.git - Do not use HTTPS URLs - only SSH URLs are supported