For Windows you can update your service by running:.For Linux it depends how you implemented the service.If you use an external configuration, such as a script or Windows Service to control your server, you'll need to update it to point to.
See also this section for what might change after a software update. Please check the documentation pages of the scanners you use for the most recent version compatible with SonarQube and your build tools. When upgrading SonarQube, you should also make sure you’re using the latest versions of the SonarQube scanners to take advantage of features and fixes on the scanner side. According to the PostgreSQL documentation: In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table they remain present until a VACUUM is done. Once you've finished a technical upgrade, you should refresh your database's statistics and rebuild your database's indices before starting SonarQube and reanalyzing your projects.įor PostgreSQL, that means executing VACUUM FULL. The relevant tables are listed in the system table all_unused_col_tabs. The SQL request is ALTER TABLE foo DROP UNUSED COLUMNS. To reclaim disk space, Oracle administrators must drop these unused columns manually. On Oracle, the database columns to be dropped are now marked as UNUSED and are not physically dropped anymore. Starting with version 6.6, there's an additional step you may want to perform if you're using Oracle. Configure your Docker instance to point to your existing database.Īdditional steps and information Oracle clean-up.Migrating from a ZIP file instance to a Docker instance If you want to move to a different edition without upgrading your SonarQube version, the steps are exactly the same as in the upgrading instructions above without needing to navigate to reanalyze your projects. Just use the appropriate edition file or Docker image tag in the upgrade instructions above. You can move to a different SonarQube edition (for example, moving from Community Edition to a commercial edition) while you're upgrading your version. Start your SonarQube instance or cluster.Switch back to the previous version of your SonarQube installation.Roll back your database to the backup you took before starting the upgrade.Shutdown your SonarQube instance or cluster.If you need to revert to the previous version of SonarQube, the high-level rollback procedure for all deployments is as follows: Upgrading from the Helm chart Reverting to the previous version
0 kommentar(er)
