We are currently using SonarQube Community Edition 9.9.2 to analyze code during development (by developers) and during the build and release process (by Jenkins). However, as both developers and Jenkins are using a single SonarQube server for analysis, we are facing an increasing number of projects, which is becoming challenging to manage.
To address this, we are considering maintaining two separate SonarQube servers: one for development and another for the build and release process in Jenkins. We are planning to use SonarQube Community Edition for development and the Developer Edition for the build and release process in Jenkins.
Is this approach acceptable? We are concerned about the potential differences in features and rules between the two editions. How can we manage these differences effectively?
If you upgrade to Developer Edition, you’ll have access to Pull Request Analysis, which is the best way to check developer changes in your codebase before merging them into production (triggered by Jenkins when a pull request is raised), rather than developers sending individual analyses.
I would also like to mention that even today, your developers would probably be better off using SonarLint to analyze their code as they type rather than trying to send analyses off to a central SonarQube server.
You might still face some scaling issues, so I have to recommend SonarQube’s Enterprise Edition, which supports increasing the number of Compute Engine workers (docs).
Thanks for the reply. It will take time to explore and move to SonarQube’s Enterprise Edition. Until then, can we follow the approach I mentioned in my post?
We are considering upgrading to the SonarQube Enterprise Edition, and we need to provide the length of our source code for this purpose. Could you please advise on how to calculate the total Lines of Code (LOC) required by our organization? Additionally, we would like to know if this value can be increased in the future as our codebase grows.
I have already tried this for Developer Edition. But got the mail to download the edition and use for trial only. Please tell how to calculate the total Lines of Code (LOC) required by our organization? We are having our source code of 100+ projects in SVN.
The evaluation of EE is a bit more guided (), so I suggest requesting an EE trial.
All of that said, if you’re code is already analyzed by SonarQube, you can check your SonarQube instance’s global Administration > System tab to see the LoC analyzed by your present SonarQube server.
), so I suggest requesting an EE trial.