To install a production platform, follow the steps below.
The SonarQube platform is made of 3 components:
- the configuration of the SonarQube instance (security, plugins settings, etc.)
- the quality snapshots of projects, views, etc.
- One for users to browse quality snapshots and configure the SonarQube instance
- One or more to analyze projects
- The SonarQube platform cannot have more than a single web server and a single database.
- For optimal performance, each component (Database, Web Server, Clients) should be installed on a dedicated machine. However, the Server and the Database can be installed on the same machine.
- Clients will scale by adding machines.
- The Database and the Clients must be located in the same network.
- The Database and the Clients must not be installed on the same machine.
- All the machines must be time synchronized.
Several database engines are supported.
Create an empty schema and a sonarqube user. Grant this sonarqube user permissions to create, update and delete objects for this schema. The charset of the database has to be set to "UTF-8" and the language to "English". Here is a sample script for MySQL.
There are two well-known engines that can be used in MySQL: MyISAM and InnoDB. MyISAM is the oldest of the two engines and is being progressively replaced by InnoDB. InnoDB is clearly faster and scales better with SonarQube when the number of projects under quality control increases. If you have been an early adopter of SonarQube, you probably have a series of table that are still using MyISAM. To improve performances, you should change the engine for all tables to InnoDB.
Once all SonarQube tables are using the InnoDB engine, the first thing to do is allocate a maximum amount of RAM to your MySQL instance with the
First, check the requirements.
<install_directory> (below) refers to the path to the directory where the SonarQube distribution has been unzipped.
Setting the access to the Database
Edit <install_directory>/conf/sonar.properties to configure the database settings. Templates are available for every supported database. Just uncomment and configure the template you need and comment out the lines dedicated to H2:
sonar.jdbc.username: =sonarqube sonar.jdbc.password: =mypassword sonar.jdbc.url: =jdbc:postgresql://localhost/sonarqube
Adding the JDBC Driver
Drivers for the supported databases (except Oracle) are already provided. Do not replace the provided drivers; they are the only ones supported.
For Oracle, copy the JDBC driver into <install_directory>/extensions/jdbc-driver/oracle.
Starting the Web Server
The default port is "9000" and the context path is "/". Parameters can be changed in <install_directory>/conf/sonar.properties:
sonar.web.host: =192.0.0.1 sonar.web.port: =80 sonar.web.context: =/sonar
Execute the following script to start the server:
You can now browse SonarQube at http:\\//localhost:9000.
Tuning the Web Server
By default, SonarQube is configured to run on any computer with a simple Java JRE. The first thing to do when installing a production instance is to use a Java JDK and activate the server mode by uncommenting the following line in <install_directory>/conf/wrapper.conf:
Advanced Installation Features
- Running SonarQube as a Service on Windows or Linux
- Running SonarQube behind a Proxy
- Running SonarQube over HTTPS
Multiple analysis clients are available:
- SonarQube Runner: recommended for all non-Maven projects
- Maven: recommended for all projects built with Maven
- SonarQube Ant Task: to integrate with projects built with Ant
- Gradle: to integrate with projects built with Gradle
- CI Engine: see Jenkins plugin or Hudson plugin or Bamboo or Bamboo plugin or AnthillPro plugin. Note that other CI engines can be used even if there is no SonarQube plugin available.