You must be the project owner to add and manage SonarQube server connections.

You can configure a job to use SonarQube from the Before Build tab and then add a post-build action (on the After Build tab) to publish its reports:

1. Open the job’s configuration page.
2. Click the Before Build tab.
3. From Add Before Build Action, select SonarQube Settings.
4. From Sonar Server, select the pre-configured SonarQube server.

   The Username, Password, and SonarQube Server URL display the selected user's details. To add a server, contact the organization administrator.

5. To provide the SonarQube project name and the SonarQube project key, expand Advanced SonarQube Settings, and update the values. Make sure that the SonarQube project key is unique.

   By default, the project key is set to <organization>_<projectname>.<jobname>and the project name is set to <projectname>.<jobname>.

6. Click the After Build tab.
7. From Add After Build Action, select SonarQube Result Publisher.
8. To use the SonarQube Quality Gate status as the build status, select Apply SonarQube quality gate status as build status.
   If the SonarQube Quality Gate status is Passed, the build is marked as successful. If the SonarQube Quality Gate status is Failed, the build is marked as failed. To learn about SonarQube Quality Gates, see https://docs.sonarqube.org/display/SONAR/Quality+Gates.
9. To create an archive file that contains the SonarQube analysis files, select the Archive Analysis Files check box.
10. Click Save.

Use the following steps to enable SonarQube for your Gradle application.

1. Add a SonarQube connection.
   See Create and Manage the Pre-Defined SonarQube Server Connection.
2. Create a build job, using the Gradle Linux 7 VM build executor.
3. In the Job Configuration page, select the Git tab, then select Git from the Add Git dropdown.
   Add a Git repository for your Gradle project files.
4. Select the Before Build tab, then select SonarQube Settings from the Add Before Build Action dropdown.
5. Select the SonarQube server you set up in step 1.
6. Expand the Advanced SonarQube Settings and examine the Project Name entry.
   If the entry contains spaces, enclose it with double quotes.
7. In the Steps tab, select Add Step, then select Gradle from the Common Build Tools dropdown list.
   1. Select Use 'gradlew' wrapper.
   2. Enter the Gradle version needed to run your project.
   3. In Tasks, add clean build.
   4. Enter the location of your build file, build.gradle.
   5. Click Turn on SonarQube.
8. In the After Build tab, add the SonarQube Result Publisher action.
9. Select Apply SonarQube quality gate status as build status and Archive Analysis Files.
10. Click Save to save the build configuration.
11. From the Build Details page, click Build Now to run the build job.
12. Once the build completes, click SonarQube Analysis Summary to display the SonarQube Analysis Summary page, which shows the SonarQube server URL for the job and the analysis summary.

You can use a Unix Shell script to enable SonarQube for Gradle applications.

1. Add a SonarQube connection.
   See Create and Manage the Pre-Defined SonarQube Server Connection.
2. Create a build job, using the Gradle Linux 7 VM build executor.
3. In the Job Configuration page, select the Git tab, then select Git from the Add Git dropdown.
   Add a Git repository for your Gradle project files.
4. Select the Before Build tab, then select SonarQube Settings from the Add Before Build Action dropdown.
5. Select the SonarQube server you set up in step 1.
6. Expand the Advanced SonarQube Settings and examine the Project Name entry.
   If the entry contains spaces, enclose it with double quotes.
7. In the Steps tab, select Add Step, then select Unix Shell from the Common Build Tools dropdown list.
   1. Click Turn on SonarQube.
   2. In the For Gradle tab, copy the Gradle command line content and paste it into the Unix Shell script area, at the top of the screen. For example:

      gradle clean build --build-file=sonarqube-scanner-gradle-multimodule/build.gradle sonarqube -Dsonar.host.url=$SONAR_URL -Dsonar.login=$SONAR_LOGIN -Dsonar.password=$SONAR_PASSWD -Dsonar.projectName=$SONAR_PROJECT_NAME -Dsonar.projectKey=$SONAR_PROJECT_KEY

8. In the After Build tab, add the SonarQube Result Publisher action.
9. Select Apply SonarQube quality gate status as build status and Archive Analysis Files.
10. Click Save to save the build configuration.
11. From the Build Details page, click Build Now to run the build job.
12. Once the build completes, click SonarQube Analysis Summary to display the SonarQube Analysis Summary page, which shows the SonarQube server URL for the job and the analysis summary.

Use the following steps to enable SonarQube for your Maven application.

1. Add a SonarQube connection.
   See Create and Manage the Pre-Defined SonarQube Server Connection.
2. Create a build job, using the Required Components Linux 7 VM build executor.
3. In the Job Configuration page, select the Git tab, then select Git from the Add Git dropdown.
   Add a Git repository for your Maven project files.
4. Select the Before Build tab, then select SonarQube Settings from the Add Before Build Action dropdown.
5. Select the SonarQube server you set up in step 1.
6. Expand the Advanced SonarQube Settings and examine the Project Name entry.
   If the entry contains spaces, enclose it with double quotes.
7. In the Steps tab, select Add Step, then select Maven from the Common Build Tools dropdown list.
   1. In Tasks, add clean install.
   2. Enter the location of your POM file, pom.xml.
   3. Click Turn on SonarQube.
8. In the After Build tab, add the SonarQube Result Publisher action.
9. Select Apply SonarQube quality gate status as build status and Archive Analysis Files.
10. Click Save to save the build configuration.
11. From the Build Details page, click Build Now to run the build job.
12. Once the build completes, click SonarQube Analysis Summary to display the SonarQube Analysis Summary page, which shows the SonarQube server URL for the job and the analysis summary.

You can use a Unix Shell script to enable SonarQube for Maven applications.

1. Add a SonarQube connection.
   See Create and Manage the Pre-Defined SonarQube Server Connection.
2. Create a build job, using the Required Components Linux 7 VM build executor.
3. In the Job Configuration page, select the Git tab, then select Git from the Add Git dropdown.
   Add a Git repository for your Maven project files.
4. Select the Before Build tab, then select SonarQube Settings from the Add Before Build Action dropdown.
5. Select the SonarQube server you set up in step 1.
6. Expand the Advanced SonarQube Settings and examine the Project Name entry.
   If the entry contains spaces, enclose it with double quotes.
7. In the Steps tab, select Add Step, then select Unix Shell from the Common Build Tools dropdown list.
   1. Click Turn on SonarQube.
   2. In the For Maven tab, copy the Maven command line content and paste it into the Unix Shell script area, at the top of the screen. For example:

      mvn clean install -f sonarqube-scanner-maven/maven-basic/pom.xml sonar:sonar -Dsonar.host.url=$SONAR_URL -Dsonar.login=$SONAR_LOGIN -Dsonar.password=$SONAR_PASSWD -Dsonar.projectName=$SONAR_PROJECT_NAME -Dsonar.projectKey=$SONAR_PROJECT_KEY

8. In the After Build tab, add the SonarQube Result Publisher action.
9. Select Apply SonarQube quality gate status as build status and Archive Analysis Files.
10. Click Save to save the build configuration.
11. From the Build Details page, click Build Now to run the build job.
12. Once the build completes, click SonarQube Analysis Summary to display the SonarQube Analysis Summary page, which shows the SonarQube server URL for the job and the analysis summary.

The VB Studio build system supports Sonarqube analysis for Java using Maven and Gradle during building and packaging. This is for Java apps, not visual applications. It doesn't provide built-in support for analyzing Javascript sources. If you need to perform a Sonarqube analysis for Javascript sources, such as those created by VB Studio, you'll need to create your own Sonarqube analysis report by using the Unix Shell builder and then uploading the results to Sonarqube.