We upgraded from Community Edition version 5.6 to Enterprise Edition version 7.6 and now we have a question about the use of versions and the ‘previous version’ setting of the leak period.
We are using SonarQube for Java, Dotnet for DotNet Core and for DotNet Framework by de msbuild scanner. For all uses we have this question.
In the community edition we used a sonar project for each solution and release version of that solution. Now we are using the Enterprise Edition we want one project key and project for each solution and we thought we could use the version parameter during analysis.
After a few weeks of using the new version (7.6) of SonarQube and redesigning our build jobs and seen some unexpected analysis results, I think we have a wrong idea about using versions during the analysis.
We always have three versions active (production, next release, changes). These currently have version numbers 23.0.46, 23.0.48 and 23.0.50 which we also use for the version parameter during sonar analysis.
Last week we had a red analysis after a change on the 23.0.46 version. Further research showed that it was compared to version 23.0.48. We did not expect this.
We expect that a change on version 23.0.46 would be compared with the latest analysis of version 23.0.46.
Are we doing something wrong with the version numbers or is our assumption indeed wrong?