@ganncamp With the new sonarqube its difficult to understand new code issues as developer may forgot the run the baseline scan, as soon as they create new branch and they push new code. After this if I run sonar scan it wont show new code issue as its first scan and since there was no baseline it will always give message: This branch could not be compared to its reference branch. See the SCM or analysis report for more details.
Developer will mostly forgot this first step to run baseline scan or there could be other issue like they may need to provide build urgently to complete testing. Earlier option sonar.branch.target was very good which was now deprecated. Can we have reference branch sonar property? Currently we can set branch level reference branch option via login into sonar portal but these manual steps are cumbersome and wont be followed diligently. Its better to have some flexible input configuration parameter to pass reference branch name during de builds.
@ganncamp I want to pass reference branch value(for new code issues) as scan parameter using sonar properties. Its flexible and can be configured in Jenkins job input parameter. Please add new sonar properties something like sonar.reference.branch=xyz. This will make life easier. I am aware that we can set reference branch using sonar portal but if not practical to login and set different reference branch for difference feature branch as these dev branches can be created from difference release branches.