Issue counts will change with same code when scanning source code for 2 times

SonarQube
1

Template for a good bug report, formatted with Markdown:

  • Versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube Enterprise Edition Version 8.9 (build 43852)
    Scanner: 4.6.1.2450-linux

  • Error observed (wrap logs/code around triple quote ``` for proper formatting)
    for the 1st code scan: sonar-scanner found 30 code issues
    for the 2nd code scan: sonar-scanner found 25 code issues

  • Steps to reproduce

  • Potential workaround

  • Scanner command used when applicable (private details masked)
    it can be:
    sonar-scanner-4.6.1.2450-linux/bin/sonar-scanner
    -Dsonar.projectKey=xxx
    -Dsonar.sources=xxx
    -Dsonar.cfamily.build-wrapper-output=output
    -Dsonar.branch.name=feature/specific_bin
    -Dsonar.host.url=xxx
    -Dsonar.login=xxx
    -Dsonar.projectVersion=yyyy_yyyyy

  • In case of SonarCloud:

    • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
    • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI, Jenkins, other)
2

Hi,

Welcome to the community!

Could you provide some detail on the issues that were missing in the second analysis?

 
Ann