Branch analysis is not working

[crcaguilerapo]

Describe the bug
When performing an analysis on a branch that is not yet associated with a PR, the new code is not being analyzed according to the project's Sonar configuration.

To Reproduce

1. Configure a Sonar project with New Code set to: Compared to master.
2. Checkout a branch derived from master.
3. Add defective code.
4. Perform an analysis of the created branch:

    sonar-scanner-5.0.1.3006-linux/bin/sonar-scanner \
      -Dsonar.organization=${SONAR_ORG} \
      -Dsonar.projectKey=${SONAR_PROJECTKEY} \
      -Dsonar.host.url=${SONAR_HOST_URL} \
      -Dsonar.token=${SONAR_TOKEN} \
      -Dsonar.branch.name=${BRANCH}

5. No malicious code detected:
   

Expected behavior
The analysis should yield the same result as when scanning the same branch associated with a PR:

    sonar-scanner-5.0.1.3006-linux/bin/sonar-scanner \
      -Dsonar.organization=${SONAR_ORG} \
      -Dsonar.projectKey=${SONAR_PROJECTKEY} \
      -Dsonar.host.url=${SONAR_HOST_URL} \
      -Dsonar.token=${SONAR_TOKEN} \
      -Dsonar.pullrequest.branch=${BRANCH} \
      -Dsonar.pullrequest.key=${PULL_REQUEST} 

Software Versions

• SonarQube Version: sonarqube:10.3-community
• Plugin Version: sonarqube-community-branch-plugin-1.18.0.jar

[gaaplex]

Thanks for the contribution!

[crcaguilerapo]

Hi @mc1arke,
Could you help me with this? Maybe I’m doing something wrong.