Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Upgrade guide

Upgrade the server

  • Stop the current Sonar server
  • Unzip the new version of Sonar in a new directory, let's say {$NEW_SONAR_HOME}
  • Copy sonar.properties and wrapper.conf files from {$OLD_SONAR_HOME}/conf to {$NEW_SONAR_HOME}/conf
  • If you have extensions, copy /extensions directory from {$OLD_SONAR_HOME} to {$NEW_SONAR_HOME}
  • Backup your database. If you use the default embedded database, copy the /data directory from {$OLD_SONAR_HOME} to {$NEW_SONAR_HOME}
  • If Sonar is deployed on JEE applications, repackage the WAR file by executing the script /war/build-war
  • Start the server
  • Clear browser cache (see issue SONAR-743).
  • Browse to http://localhost:9000 and follow setup instructions.

    For 1.5 upgrade

    Icon

    The upgrade process can take a while, depending on the size of your projects portfolio. Do not refresh the web page after having launched the setup process. This page will refresh automatically when the installation process is completed and your list of projects will appear. If you wish to monitor the process, you can look at the log file. You will know the process has completed when the 3 following lines appear:


    A big emphasize has been put on performance in version 1.5 and the server now needs less data. However, the unused data are not being removed by the migration script automatically. That is why, if you fill like you database should be shrunk, you can use the following script, after having backed up your Sonar database :

Upgrade the maven plugin

Since release 1.8, you don't have to do anything to upgrade the Sonar Maven plugin. Command is :

To find more about new Maven parameters, check the Advanced parameters section.

For 1.5 upgrade

Icon

The maven 'install' phase is not executed anymore. So the project must be previously built and installed in the local repository.


  • No labels