SonarQube accidentally updated to developer edition - how to go back to community?

SonarQube Server / Community Build
1

We were using an outdated version of the Community edition and I just went ahead and tried to updated it to the corresponding developer edition because the Helm documentation was super confusing. (Previously the helm version and the docker image version were always aligned, but that seems to have gone out the door with the recent change in versioning)

I mistook the instructions to set the community.enabled flag in helm to mean I could just download the regular LTA image and that switch would then only enable the open source features.

From what I found on the internet there was a way to move between the commercial offering and the open source version before, but I can’t find any instructions in the documentation about it.

So is my only option to rollback to a backup or can we “just switch”?

2

Hey there.

I’m assuming that you’ve upgraded your instance to SonarQube Server 2025.1 LTA.

Unfortunately, if you’ve upgraded to SonarQube Server 2025.1 LTA, you’re a couple database migrations ahead of SonarQube Community Build 25.1, meaning that a rollback is your best option.

If you were to try to start up Community Build against this database, you would get a message:

Database was upgraded to a more recent version of SonarQube. A backup must probably be restored or the DB settings are incorrect.

I’ve raised a point internally about how this could be avoided. Personally, I would love a big red sign on the /setup page that says “:warning: you’re changing edition!!!”, but maybe there are more clever ideas. :slight_smile:

We’d love your feedback on what specifically was confusing so we can prevent other users from running into the same problem!

1 Like