Sonarqube version = 7.9.1
Sonarscanner version = 22.214.171.1244
I implemented pr decoration as documented with the necessary variables passed to the sonar scanner and am seeing this happen when a master merge occurs in sonar.
I would have expected that on a master build the ‘master’ branch would have been updated versus what is seen above.
In order to get the master branch updated do I need to run the sonar scanner on master merges / builds without the pull request arguments?
/sonarqube/bin/sonar-scanner -Dsonar.projectKey= -Dsonar.projectName= -Dsonar.pullrequest.branch=master -Dsonar.pullrequest.key=null -Dsonar.pullrequest.github.repository=/ -Dsonar.scm.revision= -Dsonar.sources=.//python_scripts/ -Dsonar.tests=./test_python/ -Dsonar.python.xunit.reportPath=test_output/test-report.xml -Dsonar.python.coverage.reportPath=test_output/coverage.xml