Currently we are running Sonarqube Developer Edition 8.1, with CFamily Scanner 6.6.0 (build 13759).
Does the latest Sonarqube Developer edition (8.3.1.34397) work with the older CFamily scanner of 8.1?
I am very excited about the new dashboard of the 8.3.1 version, but I would like to stay on the current CFamily scanner that we use, as a new scanner always brings new rules, or modified thresholds, which actually ‘break’ the existing scoring.
Whatever version of the analyzer came bundled in SonarQube 8.1 will work with it. And versions up through the current 6.8 will work with it. The Plugin Version Matrix is always updated to reflect the newest compatible version. Older versions may be compatible, but since the point of the matrix is to guide upgrade decisions there’s no reason to show them.
new version of the analyzer brings new rules, new rules may break your scoring as you say and hopefully for a good reason, and, as a note, at worse it would break your quality gate only for issues in the leak period, which is supposed to be recent code.
About the break your scoring, are you more interested to not break your scoring and just have a green badge or to catch a potential bug which may crash your code?
If we add a new rule to the default quality profile it is because we believe it brings value to our users, if it is not the case we really welcome your feedback.
But the thing is, that a modified scoring is influencing the sprint outcome of the developers. So the scanner update has to be timed to a sprint end/start, not somewhere in the middle.
If 8.3 would work with the 6.6 scanner, I could roll out the new Sonarqube right away, and when the ongoing sprints are done, I could update the scanner.
Now I have to wait a few days. Not a big deal…