Skip to main content

Bitbucket Integration


Bitbucket integration is currently in beta

Cypress Cloud can integrate your Cypress tests with your Bitbucket workflow via status checks and pull request comments. A project first needs to be set up to record to Cypress Cloud to use Bitbucket integration.


Bitbucket Integration depends on your CI environment reliably providing a commit SHA (typically via an environment variable). This is not a problem for most users, but if you are facing Bitbucket integration issues with your CI setup, please make sure the git information is being sent properly by following these guidelines. If you still face issues after this, please contact us.

Installing the Bitbucket integration


Bitbucket OAuth2 applications will allow Cypress Cloud to authenticate as the user that registered the application. That means Cypress will have visibility to every Bitbucket repo you can access. If you want tighter control over the repos that Cypress will see, consider creating a service account with more limited access in Bitbucket.

  1. Visit Integrations in Cypress Cloud.
  2. Click Install Bitbucket Integration.
  3. (For beta only) You need to enable Bitbucket's development mode for your user account to continue.
  4. Continue through the Bitbucket OAuth installation flow in the popup window.
  5. Once installed, connect your projects to a Bitbucket repo.
  6. (Optional) Configure the behavior for each project.

Configuring the Bitbucket integration

Status checks

By default, Cypress will post a cypress/run commit status containing the results of the Cypress run. This will prevent your team from merging any PRs with failing Cypress tests.

Additionally, Cypress can post a cypress/flake commit status indicating whether the Cypress run contained any flaky tests. This will prevent your team from merging any PRs with flaky tests.

You can manage this behavior on your project's Project Settings page.

Pull Request comments

By default, Cypress will post a PR comment summarizing the run when the run completes. It will include test counts, run info, and a summary of tests that failed or were flaky.

You can manage this behavior on your project's Project Settings page.

Debugging Cypress Cloud Test Runs?

Don't rely on artifact representations or reproducing failing conditions locally. Replay the test as it executed during the recorded run with full debug capability using Test Replay.

Uninstalling the Bitbucket integration

You can remove this integration by visiting the Integrations → Bitbucket page of your organization. This will stop all status checks and PR comments from Cypress.