SonarQube Version: Developer Edition Version 8.0 (build 29455)
What are you trying to achieve: Analyze master branch
What have you tried so far to achieve this: Check license page, sent email to contact email
Hi Support,
We are experiencing an issue with our SonarQube analysis. We purchased a Developer License.
We have a single project and two branches defined for analysis: Develop and Master.
Develop branch passes analysis but we get the following error in master:
So you know, this is a community of interest for people interested in SonarSource products. It is not “staffed”, and people answer (or not) as time and interest allow.
The largest branch of each project is counted for licensing purposes. It sounds like your new master analysis adds a lot of LOC…?
Actually, this part is a bit odd. If the two branches are really part of the same project then only one should impact the line count. From what you’ve described, it sounds like the new analysis adds a lot of LOC to the master branch, so you’ll be right back in the same position.
Just to be sure, how about a screenshot of your Projects Management page (Administration->Projects->Management) to double-check/verify the total project count? E.G.
Thanks for the screenshot. It confirms what you said - just one project in the instance. (Sorry, but sometimes you have to back up to the “dumb” questions. )
So now I’m back to: a lot of lines have been added in master. That, or… do you have exclusions set up in the develop branch that aren’t set up/applied on master? Unfortunately there are multiple places to look:
Ann, thank you. We do not use the last two places to set exclusions.
We use:
Administration tab > Analysis Scope
Project > Administration > General Settings > Analysis Scope
What is the difference between these two?
I set some additional exclusions on the project-level and now our master branch was analyzed (1.3M LOC). I’m not entirely sure if that was the sole cause of the analysis going through. Nevertheless, thanks for your help.
The first one sets global defaults for all projects. Unless overridden, these will apply everywhere.
The second one sets/overrides at a project level. Values set here can be overridden in those other places I mention. The full hierarchy is laid out at the top of this docs page.
Yeah, right! Removing always frees space, but deleting if we made something wrong at initial configuration data at that moment doesn’t matter, in my case was that, I added a project and forgot to exclude the migration of a C# project and sonar analyzed more the 50k unnecessarily,
Thanks to this answer I deleted the project and the count started over.
)
