Try out SonarQube Community Build

You've heard about how SonarQube can help you write high quality, safer code, and now you're ready to try it out for yourself. This guide shows you how to install a local instance of SonarQube Community Build and analyze a project. Installing a local instance gets you up and running quickly, so you can experience SonarQube Community Build firsthand.

You can download SonarQube Community Build. Or try Developer Edition or Enterprise Edition for free for 14 days.

Once you're ready to set up a production instance, review the Install SonarQube Community Build documentation.

Installing a local instance of SonarQube Community Build

You can evaluate SonarQube Community Build using a traditional installation with the zip file or you can spin up a Docker container using one of our Docker images. Select the method you prefer below to expand the installation instructions:

# On Windows, execute:
C:\sonarqube\bin\windows-x86-64\StartSonar.bat
 
# On other operating systems, as a non-root user execute:
/opt/sonarqube/bin/<OS>/sonar.sh console

$ docker run -d --name sonarqube -e SONAR_ES_BOOTSTRAP_CHECKS_DISABLE=true -p 9000:9000 sonarqube:latest

Once your instance is up and running, Log in to http://localhost:9000 using System Administrator credentials:

• login: admin
• password: admin

Analyzing a project

Now that you're logged in to your local SonarQube Community Build instance, let's analyze a project:

1. Select Create new project.
2. Give your project a Project key and a Display name and select Set up.
3. Under Provide a token, select Generate a token. Give your token a name, select Generate, and click Continue.
4. Select your project's main language under Run analysis on your project, and follow the instructions to analyze your project. Here you'll download and execute a scanner on your code (if you're using Maven or Gradle, the scanner is automatically downloaded).

After successfully analyzing your code, you'll see your first analysis on SonarQube Community Build:

Your first analysis is a measure of your current code. As a developer, you focus on maintaining high standards and taking responsibility specifically for the new code you're working on. From this point, you should focus on code that has been added or changed. See Quality standards and new code for more information.