How to Install SonarQube on Rocky Linux 9

SonarQube is an open-source and self-hosted static code analysis platform for analyzing code to identify bugs, code smells and security vulnerabilities. SonarQube supports multiple programming languages and provides automated code reviews to maintain high code quality standards. It's based on Java, allowing you to deploy it on different operating systems, including containerized platforms like Docker or Kubernetes.

This article explains how to install and use SonarQube on Rocky Linux 9. You will install all required dependencies and configure SonarQube to analyze code in your projects.

Prerequisites

Before you begin, you need to:

• Have access to a Rocky Linux 9 instance with at least 4 GB RAM.
• Create a domain A record pointing to your instance's IP address. For example, sonarqube.example.com.

Install OpenJDK 17

SonarQube server requires the Java Runtime Environment (JRE) and Java Development Kit (JDK) to run on a server. The SonarQube long-term active (LTA) version 2025. It requires Java 17 or 21 to run. Follow the steps below to install OpenJDK 17 required by SonarQube on Rocky Linux 9.

1. Update the DNF package index.

   CONSOLE

   Copy

   $ sudo dnf update -y

   Explain Code

   Powered by Vultr AgentBeta

2. Install the OpenJDK 17 package.

   CONSOLE

   Copy

   $ sudo dnf install java-17-openjdk java-17-openjdk-devel -y

   Explain Code

   Powered by Vultr AgentBeta

3. Verify the installed Java version.

   CONSOLE

   Copy

   $ java -version

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   openjdk version "17.0.14" 2025-01-21 LTS
   OpenJDK Runtime Environment (Red_Hat-17.0.14.0.7-1) (build 17.0.14+7-LTS)
   OpenJDK 64-Bit Server VM (Red_Hat-17.0.14.0.7-1) (build 17.0.14+7-LTS, mixed mode, sharing)

   • If the installed Java version is below 17, run the following command to update it.

     CONSOLE

     Copy

     $ sudo alternatives --config java

     Explain Code

     Powered by Vultr AgentBeta

Create a Dedicated SonarQube User

SonarQube uses Elasticsearch for search and indexing, which requires a non-root system user. Follow the steps below to create a dedicated sonarqube user for SonarQube.

• Create a new sonarqube system user.

  CONSOLE

  Copy

  $ sudo useradd --system sonarqube

  Explain Code

  Powered by Vultr AgentBeta

  The above command creates a dedicated sonarqube user you will use to run and configure SonarQube.

Create a PostgreSQL Database for SonarQube

SonarQube supports multiple database engines including PostgreSQL which offers advanced SQL functions. Follow the steps below to install PostgreSQL if it's not installed and create a new database to use with SonarQube.

1. Install the PostgreSQL database server packages.

   CONSOLE

   Copy

   $ sudo dnf install postgresql-server postgresql-contrib -y

   Explain Code

   Powered by Vultr AgentBeta

2. Initialize the PostgreSQL database server.

   CONSOLE

   Copy

   $ sudo postgresql-setup --initdb

   Explain Code

   Powered by Vultr AgentBeta

3. Enable the PostgreSQL database server to start at boot.

   CONSOLE

   Copy

   $ sudo systemctl enable postgresql

   Explain Code

   Powered by Vultr AgentBeta

4. Start the PostgreSQL database server.

   CONSOLE

   Copy

   $ sudo systemctl start postgresql

   Explain Code

   Powered by Vultr AgentBeta

5. Log in to your PostgreSQL database server with the default postgres user.

   CONSOLE

   Copy

   $ sudo -i -u postgres psql

   Explain Code

   Powered by Vultr AgentBeta

6. Change the default postgres user password and enter a new strong password when prompted.

   PSQL

   Copy

   postgres=# \password postgres

   Explain Code

   Powered by Vultr AgentBeta

7. Create a sonardb database for SonarQube.

   PSQL

   Copy

   postgres=# CREATE DATABASE sonardb;

   Explain Code

   Powered by Vultr AgentBeta

8. Create a new sonaruser PostgreSQL user. Replace <YOUR_PASSWORD> with a strong password.

   PSQL

   Copy

   postgres=# CREATE USER sonaruser WITH ENCRYPTED PASSWORD '<YOUR_PASSWORD>';

   Explain Code

   Powered by Vultr AgentBeta

9. Grant the sonaruser full privileges to the sonardb database.

   PSQL

   Copy

   postgres=# GRANT ALL PRIVILEGES ON DATABASE sonardb TO sonaruser;

   Explain Code

   Powered by Vultr AgentBeta

10. Quit the PostgreSQL console.

    PSQL

    Copy

    postgres=# \q

    Explain Code

    Powered by Vultr AgentBeta

11. Open the /var/lib/pgsql/data/pg_hba.conf file using a text editor such as nano to modify the PostgreSQL configuration.

    CONSOLE

    Copy

    $ sudo nano /var/lib/pgsql/data/pg_hba.conf

    Explain Code

    Powered by Vultr AgentBeta

12. Change peer to trust and ident to md5 to enable password-based authentication.

    INI

    Copy

    # TYPE  DATABASE        USER            ADDRESS                 METHOD
    
    # "local" is for Unix domain socket connections only
    local   all             all                                     trust
    # IPv4 local connections:
    host    all             all             127.0.0.1/32            md5
    # IPv6 local connections:
    host    all             all             ::1/128                 md5
    ...

    Explain Code

    Powered by Vultr AgentBeta

    Save and close the file.

13. Restart the PostgreSQL service to apply the configuration changes.

    CONSOLE

    Copy

    $ sudo systemctl restart postgresql

    Explain Code

    Powered by Vultr AgentBeta

Install SonarQube

SonarQube is not available as a standalone package in the default DNF package repository sources. Follow the steps below to download and install the latest SonarQube binary on Rocky Linux 9.

1. Install Unzip to extract files from the SonarQube archive.

   CONSOLE

   Copy

   $ sudo dnf install unzip -y

   Explain Code

   Powered by Vultr AgentBeta

2. Create a dedicated sonarqube directory in a system-wide location such as /opt.

   CONSOLE

   Copy

   $ sudo mkdir -p /opt/sonarqube

   Explain Code

   Powered by Vultr AgentBeta

3. Switch to the /tmp directory to store temporary files.

   CONSOLE

   Copy

   $ cd /tmp

   Explain Code

   Powered by Vultr AgentBeta

4. Visit the SonarQube downloads page, verify the latest LTA version, and download it using Wget. For example, run the following command to download the 25.1.0.102122 SonarQube archive.

   CONSOLE

   Copy

   $ wget https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-25.1.0.102122.zip

   Explain Code

   Powered by Vultr AgentBeta

5. Extract files from the downloaded archive using Unzip.

   CONSOLE

   Copy

   $ unzip sonarqube-25.1.0.102122.zip

   Explain Code

   Powered by Vultr AgentBeta

6. Move all the extracted files to the /opt/sonarqube directory.

   CONSOLE

   Copy

   $ sudo mv sonarqube-25.1.0.102122/* /opt/sonarqube

   Explain Code

   Powered by Vultr AgentBeta

Install SonarScanner CLI

Follow the steps below to install the SonarScanner CLI on Rocky Linux 9.

1. Create the sonarscanner directory in /opt.

   CONSOLE

   Copy

   $ sudo mkdir -p /opt/sonarscanner

   Explain Code

   Powered by Vultr AgentBeta

2. Check your working directory and verify that it's /tmp.

   CONSOLE

   Copy

   $ pwd

   Explain Code

   Powered by Vultr AgentBeta

3. Visit the SonarScanner CLI releases page and verify the latest version to download using Wget. For example, run the following command to download the 7.0.2 SonarScanner archive.

   CONSOLE

   Copy

   $ wget https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-7.0.2.4839-linux-x64.zip

   Explain Code

   Powered by Vultr AgentBeta

4. Extract files from the downloaded archive using Unzip.

   CONSOLE

   Copy

   $ unzip sonar-scanner-cli-7.0.2.4839-linux-x64.zip

   Explain Code

   Powered by Vultr AgentBeta

5. Move the extracted files to the /opt/sonarscanner directory.

   CONSOLE

   Copy

   $ sudo mv sonar-scanner-7.0.2.4839-linux-x64/* /opt/sonarscanner

   Explain Code

   Powered by Vultr AgentBeta

6. Open the sonar-scanner.properties configuration file.

   CONSOLE

   Copy

   $ sudo nano /opt/sonarscanner/conf/sonar-scanner.properties

   Explain Code

   Powered by Vultr AgentBeta

7. Find the sonar.host.url property and set its value to http://127.0.0.1.

   INI

   Copy

   sonar.host.url=http://127.0.0.1

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the configuration file.

8. Enable execute permissions for the sonar-scanner binary.

   CONSOLE

   Copy

   $ sudo chmod +x /opt/sonarscanner/bin/sonar-scanner

   Explain Code

   Powered by Vultr AgentBeta

9. Link the sonar-scanner binary to the /usr/local/bin directory to enable it as a system-wide command.

   CONSOLE

   Copy

   $ sudo ln -s /opt/sonarscanner/bin/sonar-scanner /usr/local/bin/sonar-scanner

   Explain Code

   Powered by Vultr AgentBeta

10. Verify installed SonarScanner version.

    CONSOLE

    Copy

    $ sonar-scanner -v

    Explain Code

    Powered by Vultr AgentBeta

    Your output should be similar to the one below.

    17:31:54.027 INFO  Scanner configuration file: /opt/sonarscanner/conf/sonar-scanner.properties
    17:31:54.030 INFO  Project root configuration file: NONE
    17:31:54.044 INFO  SonarScanner CLI 7.0.2.4839
    17:31:54.045 INFO  Java 17.0.13 Eclipse Adoptium (64-bit)
    17:31:54.046 INFO  Linux 5.14.0-503.29.1.el9_5.x86_64 amd64

Configure SonarQube

Follow the steps below to configure SonarQube to run on your Rocky Linux 9 server.

1. Open the /opt/sonarqube/conf/sonar.properties to modify the SonarQube configuration properties.

   CONSOLE

   Copy

   $ sudo nano /opt/sonarqube/conf/sonar.properties

   Explain Code

   Powered by Vultr AgentBeta

2. Add the following configurations at the end of the sonar.properties file. Replace sonaruser, sonardb, and <YOUR_SONAR_USER_PASSWORD> with the actual PostgreSQL database details you created earlier.

   INI

   Copy

   sonar.jdbc.username=sonaruser
   sonar.jdbc.password=<YOUR_PASSWORD>
   sonar.jdbc.url=jdbc:postgresql://localhost/sonardb
   sonar.web.host=0.0.0.0
   sonar.web.port=9000
   sonar.web.javaOpts=-Xmx512m -Xms256m -XX:+HeapDumpOnOutOfMemoryError
   sonar.search.javaOpts=-Xmx1g -Xms1g -XX:MaxDirectMemorySize=512m -XX:+HeapDumpOnOutOfMemoryError
   sonar.path.data=data
   sonar.path.temp=temp

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

   The above SonarQube properties configure PostgreSQL, the default address SonarQube should listen for incoming requests 0.0.0.0, java options, and the default storage path.

3. Grant the sonarqube user ownership privileges to the /opt/sonarqube directory.

   CONSOLE

   Copy

   $ sudo chown --recursive sonarqube:sonarqube /opt/sonarqube

   Explain Code

   Powered by Vultr AgentBeta

4. Change the permissions mode to 775 to grant the /opt/sonarqube directory owner full privileges to all SonarQube files.

   CONSOLE

   Copy

   $ sudo chmod --recursive 775 /opt/sonarqube

   Explain Code

   Powered by Vultr AgentBeta

5. Open the /etc/sysctl.conf configuration file to update the memory map limit to the required SonarQube count for memory-mapped files.

   CONSOLE

   Copy

   $ sudo nano /etc/sysctl.conf

   Explain Code

   Powered by Vultr AgentBeta

6. Add the following memory configurations to the /etc/sysctl.conf file.

   INI

   Copy

   vm.max_map_count=524288
   fs.file-max=131072

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

   The above configuration updates the memory map limit to the required SonarQube count for memory-mapped files.

7. Reload the kernel parameters to apply the configuration changes.

   CONSOLE

   Copy

   $ sudo sysctl -p

   Explain Code

   Powered by Vultr AgentBeta

Create a SonarQube System Service

The SonarQube directory includes a /bin/linux-x86-64/sonar.sh startup script you can use to start or stop the SonarQube server. Follow the steps below to create a system service for SonarQube to start, stop, or restart the script.

1. Change the /opt/sonarqube SELinux content to usr_t to enable the sonaruser to execute scripts in the directory.

   CONSOLE

   Copy

   $ sudo chcon -t bin_t /opt/sonarqube/bin/linux-x86-64/sonar.sh

   Explain Code

   Powered by Vultr AgentBeta

2. Restore the /opt/sonarqube SELinux context to apply the changes.

   CONSOLE

   Copy

   $ sudo restorecon -Rv /opt/sonarqube

   Explain Code

   Powered by Vultr AgentBeta

3. Create a new sonarqube.service service file.

   CONSOLE

   Copy

   $ sudo nano /etc/systemd/system/sonarqube.service

   Explain Code

   Powered by Vultr AgentBeta

4. Add the following contents to the sonarqube.service file.

   INI

   Copy

   [Unit]
   Description=SonarQube service
   After=syslog.target network.target
   
   [Service]
   Type=forking
   User=sonarqube
   Group=sonarqube
   PermissionsStartOnly=true
   
   ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start
   ExecStop=/opt/sonarqube/bin/linux-x86-64/sonar.sh stop
   
   Restart=always
   RestartSec=10
   LimitNOFILE=131072
   LimitNPROC=8192
   
   SuccessExitStatus=143
   
   TimeoutStartSec=300
   
   [Install]
   WantedBy=multi-user.target

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

   The above service configuration uses the /opt/sonarqube/bin/linux-x86-64/sonar.sh script to start and stop SonarQube with the sonarqube user, allowing you to manage the application's runtime processes.

5. Reload Systemd to apply the service configuration changes.

   CONSOLE

   Copy

   $ sudo systemctl daemon-reload

   Explain Code

   Powered by Vultr AgentBeta

6. Enable the SonarQube service to start at boot.

   CONSOLE

   Copy

   $ sudo systemctl enable sonarqube

   Explain Code

   Powered by Vultr AgentBeta

7. Start the SonarQube service.

   CONSOLE

   Copy

   $ sudo systemctl start sonarqube

   Explain Code

   Powered by Vultr AgentBeta

8. View the SonarQube service status and verify that it's running.

   CONSOLE

   Copy

   $ sudo systemctl status sonarqube

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   ● sonarqube.service - SonarQube service
        Loaded: loaded (/etc/systemd/system/sonarqube.service; enabled; preset: disabled)
        Active: active (running) since Thu 2025-04-03 17:46:16 UTC; 12s ago
       Process: 80430 ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start (code=exited, status=0/SUCCESS)
      Main PID: 80453 (java)
         Tasks: 120 (limit: 48879)
        Memory: 1.8G
           CPU: 37.191s
        CGroup: /system.slice/sonarqube.service
                ├─80453 java -Xms8m -Xmx32m --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-op>
                ├─80481 /usr/lib/jvm/java-17-openjdk-17.0.14.0.7-2.el9.x86_64/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube/elast>
                ├─80551 /usr/lib/jvm/java-17-openjdk-17.0.14.0.7-2.el9.x86_64/bin/java -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -Djava.security.manager=allow -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headles>
                └─80601 /usr/lib/jvm/java-17-openjdk-17.0.14.0.7-2.el9.x86_64/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=/opt/sonarqube/temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL>

Configure Apache as a Reverse Proxy for SonarQube

The SonarQube web management interface is available and active on the localhost port 9000 after installation. Follow the steps below to configure Apache as a reverse proxy to securely forward all incoming connections to the SonarQube port 9000 using HTTP or HTTPS.

1. Install the Apache webserver if its not installed.

   CONSOLE

   Copy

   $ sudo dnf install httpd -y

   Explain Code

   Powered by Vultr AgentBeta

2. Enable Apache to automatically at boot.

   CONSOLE

   Copy

   $ sudo systemctl enable httpd

   Explain Code

   Powered by Vultr AgentBeta

3. Start the Apache webserver.

   CONSOLE

   Copy

   $ sudo systemctl start httpd

   Explain Code

   Powered by Vultr AgentBeta

4. Verify that the Apache mod_proxy, mod_proxy_http, and mod_proxy_balancer modules are enabled.

   CONSOLE

   Copy

   $ sudo httpd -M | grep proxy

   Explain Code

   Powered by Vultr AgentBeta

   Your output should be similar to the one below.

   proxy_module (shared)
   proxy_balancer_module (shared)
   proxy_http_module (shared)
   ..................

   Follow the steps below to enable the modules if they are not active.

   • Open the httpd.conf Apache configuration file to enable any missing modules.

     CONSOLE

     Copy

     $ sudo nano /etc/httpd/conf/httpd.conf

     Explain Code

     Powered by Vultr AgentBeta

   • Uncomment the appropiate directives to load the necessary modules:

     INI

     Copy

     LoadModule proxy_module modules/mod_proxy.so
     LoadModule proxy_http_module modules/mod_proxy_http.so
     LoadModule proxy_balancer_module modules/mod_proxy_balancer.so

     Explain Code

     Powered by Vultr AgentBeta

     Save and close the file.

5. Create a new sonarqube.conf virtual host configuration file in the /etc/httpd/conf.d/ directory to use with SonarQube.

   CONSOLE

   Copy

   $ sudo nano /etc/httpd/conf.d/sonarqube.conf

   Explain Code

   Powered by Vultr AgentBeta

6. Add the following contents to the sonarqube.conf file. Replace sonarqube.example.com with your actual domain.

   INI

   Copy

   <VirtualHost *:80>
       ServerName sonarqube.example.com
       ServerAdmin me@sonarqube.example.com
       ProxyPreserveHost On
       ProxyPass / http://localhost:9000/
       ProxyPassReverse / http://localhost:9000/
       TransferLog /var/log/httpd/access.log
       ErrorLog /var/log/httpd/error.log
   </VirtualHost>

   Explain Code

   Powered by Vultr AgentBeta

   Save and close the file.

7. Test the Apache configuration for errors.

   CONSOLE

   Copy

   $ sudo apachectl configtest

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   Syntax OK

8. Restart the Apache webserver to apply the configuration changes.

   CONSOLE

   Copy

   $ sudo systemctl restart httpd

   Explain Code

   Powered by Vultr AgentBeta

9. Allow Apache to make outgoing network connections.

   CONSOLE

   Copy

   $ sudo setsebool -P httpd_can_network_connect 1

   Explain Code

   Powered by Vultr AgentBeta

10. Allow connections to the HTTP port 80 through the default firewall configuration.

    CONSOLE

    Copy

    $ sudo firewall-cmd --add-service=http --permanent

    Explain Code

    Powered by Vultr AgentBeta

11. Reload Firewalld to apply the configuration changes.

    CONSOLE

    Copy

    $ sudo firewall-cmd --reload

    Explain Code

    Powered by Vultr AgentBeta

Secure SonarQube with Trusted SSL Certificates

Apache accepts HTTP connections for forwarding to the SonarQube localhost port 9000. HTTP uses plain text by default without any encryption. Follow the steps below to generate trusted SSL certificates to secure SonarQube with encrypted HTTPS connections between a client's browser and the webserver.

1. Install the Certbot Let's Encrypt client for Apache to generate SSL certificates.

   CONSOLE

   Copy

   $ sudo dnf install certbot python3-certbot-apache -y

   Explain Code

   Powered by Vultr AgentBeta

2. Generate a new SSL certificate using your virtual host domain. Replace sonarqube.example.com with your actual domain and admin@sonarqube.example.com with your active email address.

   CONSOLE

   Copy

   $ sudo certbot --apache -d sonarqube.example.com -m admin@sonarqube.example.com --agree-tos

   Explain Code

   Powered by Vultr AgentBeta

3. Allow HTTPS connections through the firewall.

   CONSOLE

   Copy

   $ sudo firewall-cmd --add-service=https --permanent

   Explain Code

   Powered by Vultr AgentBeta

4. Reload Firewalld to apply the configuration changes.

   CONSOLE

   Copy

   $ sudo firewall-cmd --reload

   Explain Code

   Powered by Vultr AgentBeta

Configure SELinux for SonarQube

SELinux is active on Rocky Linux 9 by default and prevents other system applications to serve content from the /opt/sonarqube directory. Follow the steps below to configure SELinux and enable Apache to serve content from SonarQube directory.

1. Check the SELinux status and verify that the current mode is enforcing.

   CONSOLE

   Copy

   $ sestatus

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   SELinux status:                 enabled
   SELinuxfs mount:                /sys/fs/selinux
   SELinux root directory:         /etc/selinux
   Loaded policy name:             targeted
   Current mode:                   enforcing
   Mode from config file:          enforcing

2. Check the /opt/sonarqube SELinux context and verify that its unconfined_u:object_r:usr_t to enable the sonarqube user to access the directory files.

   CONSOLE

   Copy

   $ ls -lZ /opt/sonarqube

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   total 128
   drwxrwxr-x. 6 sonarqube sonarqube unconfined_u:object_r:bin_t:s0  4096 Jan  7 10:30 bin
   drwxrwxr-x. 2 sonarqube sonarqube unconfined_u:object_r:usr_t:s0  4096 Jan  7 10:30 conf
   -rwxrwxr-x. 1 sonarqube sonarqube unconfined_u:object_r:usr_t:s0  7796 Jan  7 10:30 COPYING
   drwxrwxr-x. 4 sonarqube sonarqube unconfined_u:object_r:usr_t:s0  4096 Apr 22 18:18 data
   ............................

3. Verify that the SELinux boolean httpd_can_network_connect is enabled for Apache.

   CONSOLE

   Copy

   $ getsebool httpd_can_network_connect

   Explain Code

   Powered by Vultr AgentBeta

   Output:

   httpd_can_network_connect --> on

4. Restart the Apache service.

   CONSOLE

   Copy

   $ sudo systemctl restart httpd

   Explain Code

   Powered by Vultr AgentBeta

5. Restart the SonarQube service.

   CONSOLE

   Copy

   $ sudo systemctl restart sonarqube

   Explain Code

   Powered by Vultr AgentBeta

Access SonarQube

Follow the steps below to access SonarQube using its web management interface on your Rocky Linux 9 server.

1. Access your sonarqube.example.com domain in a web browser such as Chrome to open the SonarQube dashboard.

   https://sonarqube.example.com

2. Log in to SonarQube using the default admin username, and admin password credentials.

   

3. Change the default password for the admin account when prompted.

4. Click Administration within the SonarQube interface, select Security from the list of options, and click Users.

   

5. Click Create User to set up a new user for code scanning.

   

6. Click the options in the Tokens column within the new user's row.

7. Enter a new token name, set its expiry period, and click Generate.

   

8. Copy the generated token to use in your code analysis tasks.

Scan SonarQube Example Projects

Follow the steps below to clone and scan example projects from the official SonarQube repository to test the installation on your Rocky Linux 9 server.

1. Navigate to your user's home directory.

   CONSOLE

   Copy

   $ cd

   Explain Code

   Powered by Vultr AgentBeta

2. Create a new projects directory.

   CONSOLE

   Copy

   $ mkdir projects

   Explain Code

   Powered by Vultr AgentBeta

3. Navigate to the projects directory.

   CONSOLE

   Copy

   $ cd projects

   Explain Code

   Powered by Vultr AgentBeta

4. Clone the sonar-scanning-examples repository using Git.

   CONSOLE

   Copy

   $ git clone https://github.com/SonarSource/sonar-scanning-examples

   Explain Code

   Powered by Vultr AgentBeta

5. Navigate to the downloaded sonar-scanner project directory.

   CONSOLE

   Copy

   $ cd sonar-scanning-examples/sonar-scanner

   Explain Code

   Powered by Vultr AgentBeta

6. Scan the code in the directory using SonarScanner. Replace <YOUR_SONAR_TOKEN> with the actual user token you generated earlier.

   CONSOLE

   Copy

   $ sonar-scanner -D sonar.token=<YOUR_SONAR_TOKEN>

   Explain Code

   Powered by Vultr AgentBeta

   Your output should be similar to the one below when successful.

   20:38:34.725 INFO  Scanner configuration file: /opt/sonarscanner/conf/sonar-scanner.properties
   20:38:34.731 INFO  Project root configuration file: /home/linuxuser/sonar-scanning-examples/sonar-scanner/sonar-project.properties
   20:38:34.764 INFO  SonarScanner CLI 7.0.2.4839
   ...
   20:39:17.256 INFO  Analysis total time: 38.112 s
   20:39:17.259 INFO  SonarScanner Engine completed successfully
   20:39:17.628 INFO  EXECUTION SUCCESS
   20:39:17.630 INFO  Total time: 42.907s

7. Access the /projects path in your web browser.

   https://sonarqube.example.com/projects

8. Click the Example of SonarScanner Usage project.

   

9. Explore the scanned project report to verify the code's security, maintainability, code coverage, and duplication issues.

   

Conclusion

You have installed and configured SonarQube on Rocky Linux 9 to perform code analysis in projects. You scanned the example SonarQube project files using the SonarScanner and access the web management interface using your domain. For more information and configuration samples, visit the SonarQube Documentation.