| Table of content |
| Table of Contents |
Prerequisite
The only prerequisite for running Sonar is to have Java (Oracle JRE 6 onwards) installed on your machine.
Hardware Requirements
- The Sonar web server requires at least 500Mb of RAM to run efficiently.
- The amount of disk space you need will depend on how much code you analyze with Sonar. As an example, Nemo the public instance of Sonar, has more than 13 millions Lines of Code under analysis with 4 years of history. Nemo is currently running on a Amazon EC2 small instance, using about 10 Gb of drive space
Supported Platforms
Java |
|
|---|---|
| |
IBM JRE |
|
GCJ |
|
| Oracle JRockit | |
Database | |
Apache Derby |
|
| H2 | |
| |
| |
| |
| |
Application Server | |
Jetty 6 |
|
| |
| JBoss | |
| GlassFish | |
Web Browser | |
| To get the full experience Sonar has to offer, you should enable Javascript in your browser. | |
Microsoft Internet Explorer |
|
Mozilla Firefox |
|
Google Chrome |
|
Opera |
|
Safari |
|
| Table of Contents |
How to Upgrade
Note that you can directly upgrade from one version to another. For example, to upgrade from version 3.1 to version 3.5, it is not necessary to first upgrade to version 3.2, then to version 3.3, and so on.
- Check compatibility of installed plugins
- If Sonar is not connected to the Internet, check for minimum required versions listed in this page.
- If Sonar is connected to the Internet, the Update Center lists all the plugins to upgrade or to uninstall:

- Read notes below for each version
Stop Sonar:
- Download and unzip Sonar in a fresh directory, let's say {$NEW_SONAR_HOME}
- Update the content of the sonar.properties and wrapper.conf files located in the {$NEW_SONAR_HOME}/conf directory according of the content of the related files in the {$OLD_SONAR_HOME}/conf directory
- Copy the directories extensions/plugins and extensions/rules from {$OLD_SONAR_HOME} to {$NEW_SONAR_HOME} (if you see problems while starting, try to remove the copied plugins from the extensions/plugins-directory and reinstall the plugins manually via the webinterface)
- If a custom JDBC driver is used, copy it into {$NEW_SONAR_HOME}/extensions/jdbc-driver/<dialect>
- Doing a database backup is recommended
- If Sonar is deployed on a Tomcat or Jetty server, build the WAR file by executing the script {$NEW_SONAR_HOME}/war/build-war
Start server (or deploy war on server):
- Browse to http://localhost:9000/setup (replace "localhost:9000" by your own URL) and follow the setup instructions
- Analyze your projects to get fresh measures
Upgrading can take a while depending on the size of projects portfolio. To monitor the process, check the logs and the console. Upgrade is completed when an analysis has been run on project. Only at that point will you get new functionality working for sure. |
Release Upgrade Notes
Usually Sonar 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.
- Release 3.5 Upgrade Notes
- Release 3.4.1 Upgrade Notes
- Release 3.4 Upgrade Notes
- Release 3.3 Upgrade Notes
- Release 3.2 Upgrade Notes
- Release 3.1 Upgrade Notes
- Release 3.0 Upgrade Notes
- Release 2.14 Upgrade Notes
- Release 2.13 Upgrade Notes
- Release 2.12 Upgrade Notes
- Release 2.11 Upgrade Notes
- Release 2.10 Upgrade Notes
- Release 2.9 Upgrade Notes
- Release 2.8 Upgrade Notes
- Release 2.7 Upgrade Notes
- Release 2.6 Upgrade Notes
- Release 2.5 Upgrade Notes
- Release 2.4 Upgrade Notes
- Release 2.3 Upgrade Notes
- Release 2.2 Upgrade Notes
- Release 2.1 Upgrade Notes
- Release 2.0 Upgrade Notes

