{
  "doc": {
    "id": "cloud/integrations/bitbucket",
    "title": "Integrate Bitbucket with Cypress Cloud",
    "description": "Configure Bitbucket status checks and pull request comments to show Cypress test results from Cypress Cloud.",
    "section": "cloud",
    "source_path": "/llm/markdown/cloud/integrations/bitbucket.md",
    "version": "e6c8d867c21227247f14714fb5690c7c018983c5",
    "updated_at": "2026-08-08T12:39:37.868Z",
    "headings": [
      {
        "id": "cloud/integrations/bitbucket#bitbucket",
        "text": "Bitbucket",
        "level": 1
      },
      {
        "id": "cloud/integrations/bitbucket#installing-the-bitbucket-integration",
        "text": "Installing the Bitbucket integration",
        "level": 2
      },
      {
        "id": "cloud/integrations/bitbucket#configuring-the-bitbucket-integration",
        "text": "Configuring the Bitbucket integration",
        "level": 2
      },
      {
        "id": "cloud/integrations/bitbucket#status-checks",
        "text": "Status checks",
        "level": 3
      },
      {
        "id": "cloud/integrations/bitbucket#pull-request-comments",
        "text": "Pull Request comments",
        "level": 3
      },
      {
        "id": "cloud/integrations/bitbucket#uninstalling-the-bitbucket-integration",
        "text": "Uninstalling the Bitbucket integration",
        "level": 2
      }
    ]
  },
  "chunks": [
    {
      "id": "cloud/integrations/bitbucket#installing-the-bitbucket-integration",
      "doc_id": "cloud/integrations/bitbucket",
      "heading": "Installing the Bitbucket integration",
      "heading_level": 2,
      "content_markdown": "## Installing the Bitbucket integration\n\nBitbucket 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.\n\n1.  Visit **Integrations** in Cypress Cloud.\n2.  Click **Install Bitbucket Integration**.\n3.  (For beta only) You need to enable Bitbucket's [development mode](https://support.atlassian.com/bitbucket-cloud/docs/enable-bitbucket-cloud-development-mode/) for your user account to continue.\n4.  Continue through the Bitbucket OAuth installation flow in the popup window.\n5.  Once installed, connect your projects to a Bitbucket repo.\n6.  (Optional) Configure the behavior for each project.\n",
      "section": "cloud",
      "anchors": [
        "installing-the-bitbucket-integration"
      ],
      "path": "/llm/json/chunked/cloud/integrations/bitbucket.json",
      "token_estimate": 153
    },
    {
      "id": "cloud/integrations/bitbucket#configuring-the-bitbucket-integration",
      "doc_id": "cloud/integrations/bitbucket",
      "heading": "Configuring the Bitbucket integration",
      "heading_level": 2,
      "content_markdown": "## Configuring the Bitbucket integration\n\n### Status checks\n\nBy 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.\n\nAdditionally, 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.\n\nYou can manage this behavior on your project's **Project Settings** page.\n\n### Pull Request comments\n\nBy default, Cypress will post a PR comment summarizing the run when the run completes. It will include test results, run info, and a summary of tests that failed or were flaky.\n\nYou can manage this behavior on your project's **Project Settings** page.\n\n**Debugging Cypress Cloud Test Runs?**\n\nDon'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](/llm/markdown/cloud/features/test-replay.md).\n",
      "section": "cloud",
      "anchors": [
        "configuring-the-bitbucket-integration"
      ],
      "path": "/llm/json/chunked/cloud/integrations/bitbucket.json",
      "token_estimate": 208
    },
    {
      "id": "cloud/integrations/bitbucket#status-checks",
      "doc_id": "cloud/integrations/bitbucket",
      "heading": "Status checks",
      "heading_level": 3,
      "content_markdown": "### Status checks\n\nBy 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.\n\nAdditionally, 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.\n\nYou can manage this behavior on your project's **Project Settings** page.\n",
      "section": "cloud",
      "anchors": [
        "status-checks"
      ],
      "path": "/llm/json/chunked/cloud/integrations/bitbucket.json",
      "token_estimate": 96
    },
    {
      "id": "cloud/integrations/bitbucket#pull-request-comments",
      "doc_id": "cloud/integrations/bitbucket",
      "heading": "Pull Request comments",
      "heading_level": 3,
      "content_markdown": "### Pull Request comments\n\nBy default, Cypress will post a PR comment summarizing the run when the run completes. It will include test results, run info, and a summary of tests that failed or were flaky.\n\nYou can manage this behavior on your project's **Project Settings** page.\n\n**Debugging Cypress Cloud Test Runs?**\n\nDon'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](/llm/markdown/cloud/features/test-replay.md).\n",
      "section": "cloud",
      "anchors": [
        "pull-request-comments"
      ],
      "path": "/llm/json/chunked/cloud/integrations/bitbucket.json",
      "token_estimate": 105
    },
    {
      "id": "cloud/integrations/bitbucket#uninstalling-the-bitbucket-integration",
      "doc_id": "cloud/integrations/bitbucket",
      "heading": "Uninstalling the Bitbucket integration",
      "heading_level": 2,
      "content_markdown": "## Uninstalling the Bitbucket integration\n\nYou can remove this integration by visiting the **Integrations → Bitbucket** page of your organization. This will stop all status checks and PR comments from Cypress.\n",
      "section": "cloud",
      "anchors": [
        "uninstalling-the-bitbucket-integration"
      ],
      "path": "/llm/json/chunked/cloud/integrations/bitbucket.json",
      "token_estimate": 41
    }
  ]
}