TLDR overview
- Automatic analysis for Bitbucket Cloud provides a frictionless way to scan your code directly from your repositories, bypassing complex CI pipeline configuration and YAML edits.
- The feature detects critical security issues and bugs across more than 20 programming languages, including JavaScript, TypeScript, Python, Java, and C#.
- Removing technical barriers like manual pipeline configuration gives teams quick visibility into code health.
- It is a strong entry point for rapid feedback, though CI-driven analysis remains the standard for advanced production workflows.
Bitbucket Cloud repositories can now be analyzed in SonarQube Cloud without setting up Bitbucket Pipelines.
This zero-configuration feature lets SonarQube Cloud analyze your source code by interfacing directly with your Bitbucket Cloud repositories. Once a project is added, SonarQube Cloud starts analyzing it right away, with no pipeline setup. From that point forward, every commit to the default branch, and every new pull request, triggers an updated analysis. It is the fastest way for Bitbucket software developers to put code security and quality gates to work without slowing down delivery.
This expands coverage beyond our existing integrations: Bitbucket Cloud now joins GitHub, GitLab, and Azure DevOps with the same streamlined experience.
Why getting started on Bitbucket took longer
Traditionally, deep code analysis on Bitbucket required configuring Bitbucket Pipelines, editing bitbucket-pipelines.yml, and managing repository variables across projects. For fast-moving teams, or teams new to the ecosystem, that overhead often created a bottleneck that delayed adoption of code quality standards. Automatic analysis eliminates this bottleneck entirely.
With a simple setup, every step from initial import to continuous monitoring of pull requests is automated. No YAML knowledge required.
When should I use automatic analysis instead of CI-based analysis?
Automatic analysis gets you to actionable results as fast as possible. As an application grows in scale and complexity, though, moving to a CI-based pipeline is the recommended path for deeper customization.
- Dependency resolution: CI-based analysis provides deeper insight into your build environment, detecting issues in public and private dependencies, packages, and libraries that automatic analysis cannot see.
- Code coverage computation: Automatic analysis does not execute your tests, so it cannot compute code coverage. CI-based analysis runs right after your tests, giving you fresh, accurate coverage data.
- Performance and control: CI-based analysis uses compute resources tailored to your build, avoiding timeout and memory constraints. It also gives you control over analyzing non-main branches and monorepos, conditioning when analysis runs, and accessing analysis logs directly.
For more detail, see the automatic analysis documentation.
How do I get started with automatic analysis on SonarQube Cloud for Bitbucket Cloud?
For new projects follow these simple steps:
- Bind your Bitbucket Cloud workspace to a SonarQube Cloud organization with the SonarQube Cloud for Bitbucket Cloud app. If your workspace was bound before August 31, 2026, it probably uses the older SonarQube Cloud Connect app. Migrate to the new app to use automatic analysis.
- Import the repositories you want to analyze.
- Analysis starts automatically. No further configuration is needed.
- Java, C#, VB.NET, C, and C++ aren't part of the first analysis. If your repository contains them, they're added from the next analysis of your default branch.
Automatic analysis will be on by default for new projects. Enterprise plan admins can turn it off at organization level. Existing CI-based projects are unaffected and continue to run as before. For Bitbucket Cloud projects bound to SonarQube Cloud before this release, turn on automatic analysis in the project's Administration > Analysis Method page.
The bottom line
Automatic analysis gives you an immediate feedback loop the moment you import a Bitbucket Cloud repository, no configuration required. As your project moves toward enterprise-grade production, a CI-integrated setup remains the path for deeper dependency resolution, code coverage, and control over how and where analysis runs.
For setup details and the full list of supported languages, refer to the documentation.

