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?