> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/discovering/devops-platforms/bitbucket-data-center.md).

# Bitbucket Data Center

Introduction to SonarQube Server 2026.5 integration with Bitbucket Data Center.

With this integration, you’ll be able to:

* **Import your BitBucket repositories**: Import your Bitbucket repositories into SonarQube Server to easily set up SonarQube Server projects.
* **Report your Quality Gate status to your pull requests**: See your Quality Gate and code metric results right in Bitbucket so you know if it’s safe to merge your changes.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Binding to Bitbucket Data Center](/sonarqube-server/instance-administration/devops-platforms/bitbucket-data-center.md)\
  This section explains how to bind your Bitbucket Data Center workspace to your SonarQube Server instance. You need the global Administer System permission in SonarQube to perform this setup.
* [Importing your Bitbucket Data Center repository](/sonarqube-server/project-administration/creating-project/bitbucket-data-center/import-repos.md)\
  Once your Bitbucket workspace has been bound to your SonarQube instance, you can import a Bitbucket Data Center repository or monorepo to create the corresponding projects in SonarQube Server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/discovering/devops-platforms/bitbucket-data-center.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.