We would like to use the branch analysing feature only in one or two projects of SonarQube.
Is it possible to reduce licencing based on these projects? The remaining project shall be using the community edition.
And the lines of code are the total number of the biggest branches in the projects. Are they set to null after a year or can we archive projects that aren’t in use anymore?
If Archiving ist not possible, the sum of total lines constantly increase, right?
We would like to use the branch analysing feature only in one or two projects of SonarQube.
Is it possible to reduce licencing based on these projects? The remaining project shall be using the community edition.
Developer edition does not only enable branch analysis so we don’t want to start making differentiated licensing per features or per projects. We think the Developer Edition features and licensing is attractive enough to be used for all your code. Simplicity (and fairness) of the licensing is also one of our mottos.
And the lines of code are the total number of the biggest branches in the projects. Are they set to null after a year or can we archive projects that aren’t in use anymore?
If Archiving ist not possible, the sum of total lines constantly increase, right?
First of all archiving is not possible. If at least one branch of your project is still present in SonarQube even if it was not analyzed since long, it accounts for license consumption.
Then I think there’s a misunderstanding on how the LoC count works. This is not a cumulative count analysis after analysis, this is the number of LoC of the project as per the last analysis of it.
If you project has fewer LoCs after a good refactoring and you rescan. You’ll get less license consumed.
Example:
You have a project with 50K LoC. You analyze it. It consumes 50K LoC license
You refactor the project and eliminate 2000 LoC, you rescan, the new scan has 48K LoC. You license consumption with reduce from 50K to 48K LoC