Chapter 11. FAQ

This section summarizes common problems and their solutions.

Different Results in Sonargraph and SonargraphBuild

If you notice differences in the number of issues or metrics reported by SonargraphBuild, this might be due to the following reasons:

  1. The SonargraphBuild integrations for Maven and Gradle use as default the workspace information about root directories as provided by Maven or Gradle. Thus the number of root directories might be different, if the Sonargraph workspace does not contain all available root directories. If you know that all root directories contained in the Sonargraph workspace are present at build-time, deactivate this dynamic workspace configuration by setting the parameter "overrideSonargraphWorkspace" to "false".

  2. Check if test code should be part of the workspace. As default it is excluded in SonargraphBuild, because the default value of the parameter "includeTestCode" is "false".

  3. If the above points did not provide an answer, check chapter Chapter 8, Reporting Changes on how to create a detailed report about differences.

Different Results in Sonargraph and SonarQube

If you notice differences in the number of issues or metrics reported by Sonargraph and SonarQube, this might be due to the following reasons:

  1. Check the previous section and make sure that the workspace info of Sonargraph and SonargraphBuild matches.

  2. Not all Sonargraph issues can be transferred to SonarQube. See intro of chapter Chapter 9, Integration with SonarQube .

  3. If issues and metrics are created via custom scripts, the system's meta-data file must be copied over to the SonarQube server. See section Section 9.1, “Include Custom Sonargraph Metrics and Issues” for details.