External analyzer reports

How to set up the import of issues generated by third-party analyzers that integrate with SonarQube Community Build.

See alsoAnalysis parameters.

• The integration setup (except for the C family and Go) can also be done at the instance level in the UI (the project-level setup has precedence over the global-level setup). See Integration with external analyzers at instance level.

• If your analyzer doesn't integrate with SonarQube Community Build, you can import the external issues either in the generic SonarQube format or in the SARIF format. See Generic formatted reports or SARIF reports.

CloudformationCloudformation

C#

For information about the Standard Experience or MQR mode, see Standard Experience and MQR mode.

CSS

Docker

Go

Java

JavaScript/TypeScript

Kotlin

PHP

Python

Ruby

Scala

Terraform

VB.NET

Roslyn issues with an error severity automatically fail the build, and it is not recommended to run the SonarScanner for .NET’s end step if the MSBuild step fails for any reason because it will result in an essentially empty analysis, which will close all outstanding issues in the project. See Configuring the scanner for .NET for more information.

For information about the Standard Experience or MQR mode, seeStandard Experience and MQR mode.

Related pages

About external issues Generic formatted reports SARIF reports Integration with external analyzers at instance level Analysis parameters