a) currently running sonarqube community edition 10.5.1 on ec2 instance
b) deployed using docker with named volumes and external postgresql 11 database running on same instance
c)we are migrating sonarqube community build to latest stable 26.6.x.x on new ec2 instance with postgresql 15, following official update path.
d)we restored postgresql dump to new server and followed below steps:
Upgraded from 10.5.1 to 10.6(db migration using /setup done)---->upgraded from 10.6 to 24.12.100206(db migration using /setup done)---->next step per sonar’s path calculator:24.12->25.12->26.6(yet to be done)
Now we are looking to confirm whether the path we followed is correct for community build edition and whether there are any known issues or breaking changes we should be aware of before proceeding to 25.12 intermediate hop or to 26.6 as well.
Your upgrade path is indeed correct, and it’s what our calculator proposes. However, we have seen some users experience an error when trying to upgrade from 25.12 to 26.6 (in fact this known issue is even mentioned in the docs), so if you want to be sure that you don’t run into it, you could instead upgrade to 26.1 first. So: 24.12->25.12->26.1->26.6.
You should pay attention to PostgreSQL compatibility. From 25.1, PostgreSQL 11 is no longer supported, only 13-17. So make sure you upgrade PostgreSQL before that SonarQube upgrade.
Another change to look out for is that from 26.1, you will need a JDK on the server, not just a JRE. And it will need to be Java 21. You’re on docker, so as long as you don’t override this, you should be fine.
And finally, 26.2 and onward include Elasticsearch 8.x, which requires write access to /tmp. Again, on docker you shouldn’t have an issue, unless you apply some particular hardening.