Added by Simon Brandhof, last edited by Olivier Gaudin on Dec 07, 2009  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Upgrade guide

Upgrade server

  • Stop the current Sonar server 
    bin/[OS]/sonar.sh stop
Ctrl-C on Windows
  • Unzip the new version of Sonar in a fresh directory, let's say {$NEW_SONAR_HOME}
  • Copy sonar.properties and wrapper.conf files from {$OLD_SONAR_HOME}/conf to {$NEW_SONAR_HOME}/conf or configure sonar.properties
  • If you use rules extensions or your own jdbc drivers, copy the corresponding directories into /extensions from {$OLD_SONAR_HOME} to {$NEW_SONAR_HOME}
  • If you are using Sonar plugins, you should copy them to the new instance. Check the compatibility between Sonar core and the plugin before doing so.
  • 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) 
    bin/[OS]/sonar.sh start
bin/windows-x86-32/StartSonar.bat on windows
  • Browse to http://localhost:9000 and follow setup instructions.
  • Launch project analysis to refresh data.
Upgrade process

Upgrade process can take a while depending on the size of projects portfolio. Make sure that nobody accesses Sonar and do not refresh the web page during setup. The web page will be refreshed automatically at the end of upgrade. To monitor the process, checks the logs and / or the console.

Migration is completed when an analysis has been run on project. Only at that point will you get new functionality working for sure.

The first analysis after migrating to 1.11 can be very long, due to a new purge mechanism that was added.

Upgrade Maven plugin

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

mvn sonar:sonar

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