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 40 Next »

Upgrade guide

Upgrade server

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

Migration to 1.11


A purge mechanism has been implemented in Sonar 1.11 to remove unused data. This mechanism triggers at the end of every analysis. You should therefore expect that the very first analysis you run after migration takes a long time as it is going to remove a lot of those data.

During upgrade


The upgrade process can take a while, depending on the size of the projects portfolio. Do not refresh the web page after having launched the setup process as it will refresh automatically when the installation process is completed and the list of projects will appear. If you wish to monitor the process, you can look at the log file.

Using Atlassian Clover in version 1.10


The way code coverage tools are handled has slightly changed in version 1.10. The main difference is that Sonar now only authorizes one tool to be defined in general settings (as before you could use specify several) since you can override this information in project settings. Cobertura is selected by default. To use Clover, you have to set the property "General -> Code coverage plugin" to "clover".

For those who have migrated to 1.10


There was a slight issue on priority migration that is explained here.

Upgrade 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.

  • No labels