v9.9.7 (build 96285) .We have to upgrade it to version 9.9.8.100196
To upgrade it to 9.9.8 version we have gone through release notes but its quite confusing for us.
At some places they have mentioned 10.x some places 2025. LTA .It is bit confusing for us to understand this .
Release notes is not clear what changes we need to do to upgrade it to 9.9.8 version .
Updates:
After going through again what I understood is that sonarqube upgrade 9.9.8 includes fuctionality for preparing for a migration to the upcoming 10.x Long-Term Support (LTS) version.
In short they have introduced 2 ENDPOINTS in 9.9.8
/api/system/prepare_migration → endpoint to enable or disable the migration
/api/system/migrate_measures → endpoint to migrate a given number of branches or portfolios
Apart from these 2 there are 2 security fixes which mostly for improved CVSS rating .
Can someone please confirm on the above details ? because in release notes of 9.9.8 mostly they have mentioned about migration of measure tables which is I think we need to do during upgrade process of SonarQube 10.x version .
Please confirm .
In fact, you can directly upgrade from v9.9.7 to v2025.1 and skip v9.9.8 altogether, if you want.
What was originally the v10.x LTA is now v2025.1 LTA after we updated the SonarQube Server versioning scheme. If you see any old references to v10.x LTA (before we made up our minds internally), it’s effectively synonymous with v2025.1 LTA.
In v9.9.8, we introduced some endpoints to help very large instances of SonarQube perform some upgrade steps early (specifically the migration from the live_measures to the measures table, which uses a far more efficient data storage technique) in order to shorten the upgrade time.
Most users do not need to use these endpoints in order to perform the migration to v2025.1. If you’re talking to us in this Community rather than via Commercial Support, it’s likely that your instance falls into the category of instances that don’t need to perform any pre-migration steps.
My recommendation? Upgrade a non-production instance of 9.9.7 directly to v2025.1. If you don’t face any issues in the upgrade, you’re good to go for Production.
In our case, the SonarQube upgrade process is relatively quick, taking approximately 10-20 minutes or even less. Given this, do we need to consider migrating the measure tables? As per your suggestion If we continue without migrating measures table, will there be any performance impacts or other issues during future upgrades?
This table migration is pre upgrade steps for every upgrade to make upgrades faster? or this is just one time activity which has to perform before upgrading to 10.x or 2025.1 LTA ?
From my understanding, the two endpoints introduced in version 9.9.8 are primarily intended for users with large SonarQube instances. However, based on your suggestion, if we choose not to migrate the live_measures table to the measures table, will this lead to any complications in future upgrades?
Is table migration necessary regardless of the size of the SonarQube instance?