Must-share information (formatted with Markdown):
** SonarQube Enterprise 8.2
** sonar-scm-git plugin version: 1.11.1 (build 2008)
- We are transitioning our organization to the Enterprise edition of Sonar. We have a Quality Gate in place with conditions only around New Code. We have many feature branches already in progress, prior to the transition, and are looking for a good way to evaluate if these branches are compliant with the gate prior to merge back to master.
- We thought it would be straightforward to create a new branch off of master, let that branch build and be analyzed by SonarQube and then merge the old branch into the new one. However, when we do this we are seeing no coverage on “0 New Lines to Cover” on the New Code tab. We have tried a few other merge approaches as well. If we squash the commits on merge, it appears to work (we get coverage and new lines are detected). However, we would prefer it if we could get a standard merge to reliably show our issues and coverage on new code.
I should mention that we are using the “Previous Version” method for setting the new code period.