Skip to main content
HealOps queries Bitbucket to retrieve recent commits, file contents, and code search results — helping trace which change in a Bitbucket-hosted repository triggered an incident.

Prerequisites

  • Bitbucket Cloud account
  • App password with repository read access

Setup

Option 1: Interactive CLI

Select Bitbucket when prompted and provide your workspace, username, and app password.

Option 2: Environment variables

Add to your .env:

Option 3: Persistent store

Creating an app password

  1. In Bitbucket, go to Personal settingsApp passwords
  2. Click Create app password
  3. Give it a label (e.g., healops)
  4. Enable the following permissions: Repositories: Read
  5. Copy the generated password
The workspace slug is the identifier in your Bitbucket URL: https://bitbucket.org/<workspace>/

Investigation tools

When HealOps investigates a Bitbucket-related alert, three tools are available:
  • Commits — retrieves recent commits for a repository, optionally filtered by file path
  • File contents — fetches the contents of a file at a specific revision
  • Code search — searches code across the workspace or a specific repository
All operations are read-only.

Verify

Expected output:

Troubleshooting

Security best practices

  • Use an app password rather than your account password — app passwords can be revoked individually.
  • Scope permissions to Repositories: Read only.
  • Store credentials in .env, not in source code.