Skip to main content
Bitbucket Cloud support uses one deployment-scoped OAuth client. The authorized account’s accessible workspaces define the repositories Roomote can sync. Bitbucket Server and Data Center are not supported.

​
Create a Bitbucket OAuth client

In the Bitbucket Cloud workspace that owns the repositories, open Workspace settings → Apps and features → OAuth clients, then create an OAuth client. Set its callback URL to:
Grant these scopes: Save the client values in setup or deployment environment variables:
BITBUCKET_BASE_URL is optional and defaults to https://bitbucket.org. BITBUCKET_WEBHOOK_SECRET is optional; Roomote generates one when webhooks are first configured.

​
Connect and sync repositories

After saving the consumer values, an admin is redirected to Bitbucket to authorize the deployment. The callback exchanges and encrypts the OAuth connection, synchronizes all accessible repositories, and registers repository webhooks (including repo:commit_status_created and repo:commit_status_updated for Pipelines) before returning to setup. Bitbucket-backed tasks use x-token-auth for Git HTTPS credentials. OAuth API requests use bearer authentication.

​
Personal account linking

Users may link personal Bitbucket accounts separately for commenter identity and access-policy checks. Linked accounts do not provide deployment source control credentials.

​
CI Failure Triage

When enabled, Roomote triages failed default-branch Bitbucket Pipelines via repo:commit_status_created / repo:commit_status_updated webhooks and Manual Run now. Only environment-mapped repositories are included.

​
Current limits

  • Bitbucket Cloud only. Server and Data Center are not supported.
  • One deployment OAuth connection is supported.