Question on hitting license limit after checking out the source code into a new location

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • SonarQube 7.8.0.26217, Developer Edition, 500K LOC license
  • Change location of the scanned source without doubling LOC license count
  • I currently have the following properties in the scanner:

sonar.projectKey=SQLServer_Trunk_StoredProcs
sonar.projectName=SQLServer_Trunk_StoredProcs
sonar.projectVersion=1.0
sonar.sources= C:/src/ SQLServer_trunk/stored_procs
sonar.projectBaseDir= C:/src/ SQLServer_trunk/stored_procs

I need to automate the scanner by checking out the same source tree under Jenkins (CI server) workarea so that my configuration would have to become the following:

sonar.projectKey=SQLServer_Trunk_StoredProcs
sonar.projectName=SQLServer_Trunk_StoredProcs
sonar.projectVersion=1.0
sonar.sources= C:/Jenkins/workarea/ SQLServer_trunk/stored_procs
sonar.projectBaseDir= C:/Jenkins/workarea/ SQLServer_trunk/stored_procs

Will this create a problem with licensing? Meaning, would it cause SonarQube to double LOC license count? If it would, what can I do to move the code to the new location without impacting the license LOC count?

Thank you

2

Hi,

This will not count to your LOCs. The way LOCs are computed is by picking up the branch with the highest LOC count for each project. Here, you are just telling the scanner where to find the sources if it executes in Jenkins: if you use the same project key, then no additional project will be created and therefore no more LOCs are counted.

Hope this is clear. On another note, you are on version 7.8 which is not anymore supported, as the last Long Term Support version is 7.9. Why not upgrading?

Cheers!