What’s synced
- Pull requests and their metadata
- Commits and code changes
- Code reviews and comments
- Team members and workspace structure
- Repository information
- Pipeline and deployment data (Bitbucket Pipelines)
Connecting Bitbucket Cloud
1
Start connection
Go to Data and click Connect on Bitbucket
2
Authorize Weave
Sign in to Bitbucket and authorize the Weave app
3
Select repositories
Choose which repositories to sync from your workspaces
4
Wait for sync
Initial sync may take several minutes depending on repository size
Permissions required
Weave requests the following Bitbucket permissions:- Repository — Read access to repositories, pull requests, and commits
- Account — Read access to your account information and email
- Workspace — Read access to workspace members and teams
Multiple workspaces
You can connect multiple Bitbucket workspaces. Each workspace’s data will be synced separately.Choosing the account to connect
Weave connects to Bitbucket Cloud through one Bitbucket account per Weave organization, and lists repositories from every workspace that account can access.- The account doesn’t need to be a workspace admin. It needs to be a member of each workspace you want to sync, with at least read access to the repositories you want to sync.
- To sync repositories from several workspaces, connect an account that belongs to all of them. Many teams use a shared service account so the connection doesn’t depend on one person.
- Reconnecting Bitbucket with a different account replaces the existing connection. Before you switch, make sure the new account can access every repository you already sync.
Sync frequency
Weave syncs Bitbucket data via polling every 3 hours.Bitbucket Data Center (self-hosted)
To set up a self-hosted Bitbucket Data Center instance, you need to create an Application Link in Bitbucket. This allows Weave to authenticate with your instance and access your repositories.Setup steps
1
Log in as administrator
Log in to your Bitbucket Data Center instance as an administrator
2
Navigate to Application Links
Go to Administration → Application Links
3
Create link
Select Create link and choose External application with direction Incoming
4
Configure application
Fill in the following details:
- Name: Weave
- Redirect URL:
https://app.workweave.ai/api/bitbucket/oauth/callback - Permissions:
- Projects: Admin
- Repositories: Read
5
Save and copy credentials
Select Save and copy the Client ID and Client secret
6
Connect in Weave
Go to the Weave data sources page
On the Bitbucket card, click Connect self-hosted
Enter your instance URL, Client ID, and Client secret
7
Select repositories
Choose which Bitbucket projects and repositories to sync
Permissions required
Weave requires the following permissions for Bitbucket Data Center:- Projects: Admin — Required to fetch workspace members and list projects
- Repositories: Read — Read access to repository data (commits, PRs, etc.)
Network configuration
If your Bitbucket Data Center instance is behind a firewall, you may need to allowlist Weave’s IP addresses. See the reference page for a list of IP addresses to allowlist.Automatic repository sync
When you select all available repositories during setup, Weave automatically enables auto-sync for new repositories. This means any new repositories created on your Bitbucket instance will be automatically added to Weave without manual intervention. If you manually remove individual repositories after the initial setup, auto-sync is disabled. To re-enable it, select all available repositories again.Version requirements
Bitbucket Data Center requires version 7.0 or later for full feature support. Weave needs network access to your Bitbucket instance.
Cloud vs Data Center differences
Unlike Bitbucket Cloud, which uses a centralized OAuth application registry, Bitbucket Data Center requires you to manually create an Application Link on your specific instance. This is why you must provide the Client ID and Secret generated by your instance rather than clicking a “Connect” button.Supported features
Code review metrics
- Pull request cycle time and velocity
- Code review turnaround and quality
- Comment analysis and resolution tracking
- Review depth and thoroughness
Code quality tracking
- Lines of code and code output
- Code turnover and churn analysis
- Bug and revert tracking
- AI-assisted code detection (via Bitbucket Pipelines)
CI/CD metrics
- Bitbucket Pipelines success rates and frequency
- Deployment tracking (if using Bitbucket Deployments)
- Build and test performance
Team collaboration
- Engineer activity and contributions
- Team structure from Bitbucket workspaces and groups
- Review participation and patterns
Bitbucket vs. GitHub terminology
Troubleshooting
Sync is slow or incomplete
Sync is slow or incomplete
If data isn’t syncing properly:
- Check that repositories are not archived
- Verify webhook configuration in repository settings
- Ensure your Bitbucket plan includes API access
- Contact support if sync is stuck for more than 30 minutes
Missing team members
Missing team members
If team members aren’t appearing:
- Ensure members have commits or pull requests in connected repos
- Verify members have public email addresses or linked Weave accounts
- Check that members have not been removed from the workspace
- Re-sync the integration to refresh team member data
Bitbucket Data Center issues
Bitbucket Data Center issues
For self-hosted Bitbucket instances:
- Ensure Weave can reach your Bitbucket instance (check firewall rules)
- Verify the Application Link is configured correctly
- Check that API rate limits are not being hit
- Review Bitbucket logs for authentication or permission errors
Data privacy
Weave syncs only metadata about your pull requests, commits, and reviews. We do not store your source code or repository contents.Related integrations
- GitHub — Alternative Git platform
- GitLab — Alternative Git platform
- Jira — Often used with Bitbucket for issue tracking
- Confluence — Often used with Bitbucket for documentation