Jenkins SonarQube

Search the Azure Marketplace for "SecureAnyCloud Jenkins SonarQube" and select Create. Choose the Standard_B4ms size and your VNet and subnet. Make sure the NSG allows inbound TCP 22 and TCP 80 from your trusted CIDR.

Connect to the VM as azureuser:

ssh azureuser@<public-ip>

Run the command below to check the four services. All of them are enabled and started on first boot.

for s in postgresql sonarqube jenkins nginx; do printf '%-14s %s (%s)\n' "$s" "$(systemctl is-active $s)" "$(systemctl is-enabled $s)"; done

First boot rotates every secret and writes the new values to a file that is unique to this VM. Read it with sudo:

sudo cat /var/lib/sac/secrets/sac-credentials.txt

The file (mode 0600 root:root) contains JENKINS_URL and JENKINS_ADMIN_PASSWORD, SONARQUBE_URL and SONARQUBE_ADMIN_PASSWORD, and SONARQUBE_ANALYSIS_TOKEN. Every value is unique to your VM.

Browse to http://<public-ip>/ and sign in with admin and the JENKINS_ADMIN_PASSWORD from Step 4. The dashboard lists the pre-seeded sonarqube-analysis-demo pipeline.

Browse to http://<public-ip>/sonar and sign in with admin and the SONARQUBE_ADMIN_PASSWORD from Step 4. The same nginx front door serves SonarQube under the /sonar path.

To confirm the server is up without signing in, run:

curl -s http://localhost/sonar/api/server/version; echo
curl -s -o /dev/null -w 'sonar /health: %{http_code}\n' http://localhost/health

The seeded sonarqube-analysis-demo pipeline demonstrates the whole loop. Open it in Jenkins. The Stage View shows the SonarQube analysis and Quality gate stages.

Then open SonarQube. The analysed project appears there with its quality gate result.

You can verify the same thing from the shell. The bundled check runs a real sonar-scanner analysis with the per-VM token. It confirms that SonarQube processed the analysis and evaluated the gate:

sudo /usr/local/sbin/jenkins-sonarqube-integration-check.sh

The SonarQube-to-Jenkins webhook that waitForQualityGate relies on is pre-configured. In SonarQube, open Administration > Configuration > Webhooks to see the Jenkins webhook and its deliveries.

On the Jenkins side, a SonarQube server installation and a SonarScanner tool are already configured under Manage Jenkins > System and Tools. Your own pipelines can use the integration with no setup:

pipeline { agent any stages { stage('SonarQube analysis') { steps { script { def scannerHome = tool 'SonarScanner' withSonarQubeEnv('SonarQube') { sh "${scannerHome}/bin/sonar-scanner -Dsonar.projectKey=my-app" } } } } stage('Quality gate') { steps { timeout(time: 5, unit: 'MINUTES') { waitForQualityGate abortPipeline: true } } } } }

Point a job at your own Git repository and add a sonar-project.properties file, or pass -Dsonar.sources=.... The analysis, token and quality-gate feedback then work with no further configuration.

Print the Jenkins, SonarQube and Java versions:

echo "Jenkins: $(curl -sI http://localhost/login | awk '/[Xx]-[Jj]enkins:/{print $2}' | tr -d '\r')"
echo "SonarQube: $(curl -s http://localhost/sonar/api/server/version) (Community Edition)" java -version 2>&1 | head -1