FAQ

This description is only valid for cxx plugin version 1.x

This is the list of frequently asked questions and less frequently given answers:

===

Q: I don't see any violations after running a SonarQube analysis

A: Possible solutions include:

• The cxx plugin does not run any static analysis tools itself, make sure that the reports are generated before the analysis (see Running tools).
• Be certain the properties are correctly set and the used paths are absolute or relative to the project root.
• Be sure that the tools are run in the same location as the analysis. And that you don't move reports between locations with different paths. To ensure that you're not facing a path mismatch issue, run the analysis with debug enabled (using -X parameter) and check the output.

===

Q: SonarQube fails to start with error messages: Cannot insert duplicate key row in object 'dbo.rules'

A: This problem can occur when using MS SQL database configured to be case insensitive. Make sure database is set to be case sensitive and restart SonarQube. For more information check database requirements for SonarQube: Requirements

===

Q: Why does SonarQube alternate between two different values for coverage, although the code didn't change inbetween?

A: This effect can be observed if you feed multiple coverage reports which include coverage data for same source files. To prevent this, merge the coverage report outside Sonar before feeding them.

===

Q: ERROR: Caused by: File [...] can't be indexed twice.

A: In case of below error you have to verify your exclusion/inclusion properties. Please check that inclusion/exclusion patterns produce disjoint sets for source and test files

ERROR: Caused by: File [...] can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files

An example could look like this:

sonar.sources=.
sonar.tests=.
sonar.test.inclusions=**/*Test*/**
sonar.exclusions=**/*Test*/**

===

Q: Unable to parse UTF-8 with BOM files.

A: Reading files with a specific file encoding is a SonarQube core feature. Normally you set the source file encoding in the project configuration with sonar.sourceEncoding. The list of available encodings depends on your JVM. See http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html. Currently (SonarQube 5.1) file encodings with BOM are not supported by the core. You have to use another encoding or to remove the BOM with a script before reading it with SonarQube.

===

Q: How to collect compiler log without affecting return code nor realtime logging?

A: One solution can be to use the pipefail feature:

mkdir -p reports
set -o pipefail
make all | tee reports/gcc.log

An other could be the script command:

mkdir -p reports
script -e -c "make all" reports/gcc.log