Sonarqube: Downgrade from Developer to Community

SonarQube Server / Community Build
, ,
1

  • Downgrade from Sonarqube Developer to Community v25.2.0.102705

  • Another project needed our Dev license, so we’re switching to community due to priority

  • how is SonarQube deployed: zip

  • So we backed up the existing db (SQL svr) → restored to new db: sonar_community and installed community. Following screen popped up and we completed it

    image
    image630×520 51.2 KB

  • We were able to launch and see our projects:

    image
    image1381×616 111 KB

  • Opened the project and it shows no issues. I have checked that issues are there in Issues table wrt same project id

    image
    image1920×1080 196 KB

  • The issues/details are not available for any existing project (however appears for newly scanned ones)
    Clicked to check list of rules: shows 0

    image
    image1205×177 16.3 KB

    image
    image1596×984 59 KB

  • what are you trying to achieve
    Downgrade to community & see the old scans with details
    What else to perform to see existing issues from existing projects?

  • Another issue: We issued a new scan with new project name (we can see list of issues)
    However, the reported issues in community are lesser than in developer, is this because the rules are less?

2

Hey there.

This can happen because SonarQube stores some internal state—including indices—produced by Elasticsearch that may not be correctly refreshed following edition changes or DB migrations.

(docs)

In your case, try the following steps:

  1. Stop SonarQube if it’s running.

  2. Delete the contents of the data/es8 directory (this is where SonarQube’s Elasticsearch indices are stored). This will force SonarQube to rebuild its indices from the restored database on the next startup:

    rm -rf <your-sonarqube-installation>/data/es8

  3. Start SonarQube again.

Yes, the number of issues reported can differ between Developer Edition and Community Build. Community Build supports a subset of languages and rules compared to Developer. Advanced rules and some language support are not available in Community, so some issues previously reported may not appear.

:warning: Only the latest version of SonarQube Community Build is considered active, so you’ll need to upgrade and see if the situation is still replicable before we can help you.

Your upgrade path is:

25.2 → 25.5

You may find these resources helpful:

3

Hi Colin, thanks for answering. We’ll try to upgrade and try reindexing