Skip to main content
Bitbucket Data Center integration lets Blitzy connect to your self-hosted instance for code analysis, branch creation, commits, and pull request management. If you use Bitbucket Cloud (bitbucket.org), see Bitbucket instead.

Setup

1

Create an application in Bitbucket

In your Bitbucket Data Center instance, navigate to Administration > Application Links. Create a new application link and note the Application ID and Secret that are generated. The secret is shown only once during creation - store it securely.
2

Open the Blitzy connection form

Navigate to Settings > Integrations in your Blitzy dashboard and click Connect Bitbucket Data Center. The Bitbucket Data Center connection form will appear.
3

Enter connection details

Fill in the three required fields:
  • Bitbucket URL - Your organization’s Bitbucket instance URL (e.g., https://bitbucket.yourcompany.com)
  • Application ID - The ID from Administration > Application Links in your Bitbucket instance
  • Secret - The secret generated when you created the application link
4

Choose sharing

After connecting, choose whether to keep the integration private (Just me) or make it available to your team (Share with team). Click Done to finish.
You must have System Administrator access to your Bitbucket Data Center instance to create application links.
The application secret is shown only once when creating the application link. If you lose it, click Change secret in the Blitzy connection form to generate a new one.

Permissions

The Blitzy Bitbucket Data Center integration requires the following permissions, scoped to the minimum level needed.

Permission Mapping Reference

Differences from Bitbucket Cloud

Network Requirements

Your Bitbucket Data Center instance must be accessible from Blitzy’s platform over HTTPS. If your instance is behind a firewall or VPN, work with your network team to allow inbound connections from Blitzy’s IP ranges. Contact [email protected] for the current IP allowlist. For Bitbucket-specific troubleshooting (OAuth errors, permission issues), see Troubleshooting.