which versions are you using : Currently using Sonarqube version 9.9.8
using this plugins currently : sonar-pmd-plugin-3.5.1 , sonar-detekt-2.5.0 , sonar-dependency-check-plugin-4.0.1 , sonar-findbugs-plugin-4.3.0 , esql-plugin-3.5.0
how is SonarQube deployed: image built via docker and deployed through terraform
what are you trying to achieve : Trying to upgrade to 9.9.9
Is there any Java version related changes in 9.9.9 ?
Also as we gone through 9.9.9 release notes , we got to know that it almost contains bug fixes regarding measures migration . Could you please tell more about this measures ?
do we also need to do this measures migration before proceeding to 9.9.9 upgrade or it is for 2025.* . * versions?
if measures migration is not required for our sonarqube instance then can we skip 9.9.9 ?
Measures migration is required for all instances, but unless yours is very, very large, this won’t be an issue. The 9.9.9 changes allow a kind of pre-migration to run in the background before the move to 2025.
What I understand is that if the SonarQube system is very large, the migration process might be more complex and could potentially cause issues. However, for most systems that aren’t extremely large, the migration process will be straightforward and manageable.
How can we identify whether a system is large or small? Are there specific metrics to classify a system as large or small?
Additionally, you mentioned that version 9.9.9 allows pre-migration tasks to run in the background, which is required for version 2025. However, you also mentioned that we can skip version 9.9.9 and go directly to version 2025. This is a bit confusing. Could you please clarify? Are the changes in version 9.9.9 only necessary for large SonarQube instances? OR for small instances measure migration is going to take place as background task?
I suggest running an upgrade - with a copy of your DB - in a test environment. If you find the duration too long, then you may be interested in the 9.9.9 upgrade.
Are the changes in version 9.9.9 only necessary for large SonarQube instances? OR for small instances measure migration is going to take place as background task?
Thanks for confirming but then how the measure migration will happen in small SonarQube instances? for small instances measure migration is not required?
On small instances the measures migration will be performed during the upgrade.
If you are not using any particular plugin in your instance, everything will be smooth as any other upgrade.
If you use “dependency check” plugin and you are importing the html report into SonarQube (or any other plugin that stores very large measures), then it may require a little bit more time and memory, but as far as I know, there is now a check during the migration process that won’t migrate large measures to avoid performance issues after the upgrade.
Thanks @acalero for quick response.
You mentioned that there are checks during the migration process to prevent the migration of large measures to avoid performance issues after the upgrade. My question is: will not migrating these measures due to these checks cause any issues post-upgrade?
Then you currently have HTML-formatted reports stored as measures. The measures table was never intended for that, and with some optimizations we’ve made in recent versions that mis-use slows the interface to a crawl. So they get cleaned out. So the only post-upgrade “issue” would be that you no longer have those HTML-formatted reports. But the raw measure values should still be visible in SonarQube.
I’m not familiar with the plugin, but I think there might be an option to stop generating & trying to store those HTML reports. If so, you might want to toggle it.
I am asking with respective of SonarQube not plugin, do we need to make any changes at our end as HTML-formatted reports are going to get eliminated in upcoming version and only raw values will be visible or it will get taken care in upcoming version