> 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-cloud/analyzing-source-code/ci-based-analysis/circleci.md).

# CircleCI

A quick link to the SonarQube Cloud Orb which can be used with any linux based docker image that includes the command line tools ‘curl’ and ‘unzip’.

Once your project is created and initiated from the repository you selected, follow our [official Orb Quick Start Guide](https://circleci.com/orbs/registry/orb/sonarsource/sonarcloud) to set up your project using Maven, Gradle, and other build technologies. Check also [our Orb’s readme](https://github.com/SonarSource/sonarcloud-circleci-orb/blob/master/README.md).

## Limitations

* Make (for C/C++ projects) and MSBuild are not yet supported.
* The Orb is currently available only for Linux and x64 architecture.

## Using the US region

To use the [US region](/sonarqube-cloud/getting-started/choosing-your-region.md), you must set the `sonar.region` property to `us`. Whether you use our Orb or the SonarScanner CLI directly in your CircleCI, we recommend that you add the `SONAR_REGION` environment variable to your [CircleCI context](https://circleci.com/docs/contexts/).

## Troubleshooting

**Analysis time is unexpectedly slow**

If analysis is unexpectedly slow or appears stuck when running on CircleCI, check whether your pipelines use blobless or otherwise partial Git checkouts. Configuring a full checkout by changing any occurences of the `checkout` step in the CircleCI config might help restore normal performance:

```yaml
- checkout:
    method: full
```


---

# 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-cloud/analyzing-source-code/ci-based-analysis/circleci.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.