Other CIs

Running an analysis on a CI provider other than those with specific integrations.

Running an analysis on another CI provider

1. Integrate the SonarScanner analysis into your build pipeline as explained in the corresponding scanner section:

   • SonarScanner for .NET

   • SonarScanner for Maven,
   • SonarScanner for Gradle

   • SonarScanner for NPM

2. If necessary, adjust the Analysis scope or customize other default Analysis parameters.
3. Start and test the analysis.
4. Add the branch analysis or pull request analysis to your pipeline. See the Branch analysis setup and Pull request analysis pages for more information.

Here is an example of a configuration for pull requests in a CI job:

sonar.pullrequest.base=main
sonar.pullrequest.branch=feature/my-new-feature
sonar.pullrequest.key=5

If your project is bound to Azure DevOps and you're running analysis outside of Azure Pipelines, you must also pass Azure DevOps-specific parameters explicitly. Azure Pipelines detects these values automatically from its environment; other CI systems don't. See Azure DevOps PR decoration parameters for more information about these parameters.

Failing a pipeline job when the quality gate fails

You can configure the SonarScanner to wait for the quality gate result. This setting will force the pipeline to fail if the quality gate fails.

To do so:

1. Set the sonar.qualitygate.wait analysis parameter to true.
2. You can set the sonar.qualitygate.timeout analysis parameters to the number of seconds that the scanner should wait for a report to be processed. The default is 300 seconds.

For general information on setting up analysis parameters, see Configuration overview.