SonarQube Upgrade process is automated, and below 5.2 you can upgrade from any version to any version. But starting from SonarQube 5.2, the migration scripts are only available from the nearest LTS.
That means that if you want to move from an version prior to SonarQube 4.5 to 5.2, 5.3, 5.x, you must first migrate to at least SonarQube 4.5.x LTS.
Examples:
It is very important that you backup your database (step #7 in the guideline below) in case anything unexpected happens during the migration. |
Stop the SonarQube server
Start the web server
If you use external configuration, such as a script or Windows Service to control your server, you'll need to update it to point to NEW_SONARQUBE_HOME. |
The time to complete an upgrade will vary based on the size of the projects portfolio. From 5.0 forward, upgrade time can be significantly impacted by the recreation of the Elasticsearch indices, which could take one or more hours, again depending on the size of the projects portfolio. You can monitor the progress of both the database upgrade and the ES index creation by watching the server log: NEW_SONARQUBE_HOME/logs/sonar.log An upgrade is complete when an analysis has been run on a project. Only then will you see the new functionality. |
If, for some reasons, your upgrade failed, you can roll back by:
Restarting the previous version of the web server
Usually the SonarQube releases come with some specific recommendations for upgrading from the previous version. You have to read the upgrade notes for all versions between your current version and the target version.