gitlab-devops.md

@@ -54,4 +54,68 @@ In Gitlab you need to create a Webhook for Jenkins. Go to Project Settings > Int
 Created Webhook.
 Test the connection. I tested the connection using Push events. You may need to [enable same network-traffic](https://docs.gitlab.com/ee/security/webhooks.html). You should see a success message in GitLab. 
 
+### Sonarqube
+#### Installing Sonarqube
+I used Docker-compose to install sonarqube:
+```
+ sonarqube:
+    image: 'sonarqube:lts'
+    ports:
+      - 9000:9000
+      - 9092:9092
+    container_name: sonarqube
+
+```
+You should be able to access your sonarqube on port 9000.
+
+#### Configuring Sonarqube to work with Jenkins
+ 
+You need to create a project in Sonarqube. Log in to Sonarqube the default login is admin/admin. You can create a project in Administrator > Projects > Projects Management > Create Project. 
+Add a name to your project and a key which Jenkins will use to connect to Sonarqube. I named mine dev and set the key to dev2. 
+![image](/uploads/8bfd200e4695e2d52308b8b418bf250d/image.png)
+![image](/uploads/8f51d5d8c699fad898ce80da32da518a/image.png)
+Create project.
+
+On Jenkins go to Manage Jenkins > Manage Plugins and install SonarQube Scanner for Jenkins:
+![image](/uploads/ec6487e9d18241a3931c9444f4f3171b/image.png)
+Sonarqube scanner.
+
+You need to restart Jenkins.
+After that go to Manage Jenkins > Global Tool Configuration > SonarQube Scanner :
+![image](/uploads/002b0fb1dd807f23358b03fffbe7676d/image.png)
+You need to set a name to your sonarqube scanner and how it is installed to Jenkins I selected the default Maven. 
+
+You should also set Maven installation:
+![image](/uploads/24286a8dc2805ed56dc19fc13b65b690/image.png)
+Maven installation.
+
+Go Back to Manage Jenkins and go to Configure System:
+Add SonarQube server:
+![image](/uploads/a19ad28ce71b7e0b49bc026f98344743/image.png)
+
+Add a name to your server-connection and your url. You also should create a token for your connection. For this go to Sonarqube and Administrator > My Account > Security :
+Generate a new token and name your token. You should also save it to secure location because you won't be able to access it from here again.
+![image](/uploads/30daa0fec957f01e9dfed032b38ea051/image.png)
+Created token. 
+
+Now to integrate the sonarqube to the GitLab project we need to go to the Jenkins project where we added the GitLab connection and go to Configure > Build :
+
+![image](/uploads/b50571856433333e3ef5176aae3c8a51/image.png)
+Add analysis properties to match your SonarQube: Now add the project name, key and the version of Sonarqube you are running. You can also enter the project version. Save the settings.
+
+Now you should be able to build your project using Jenkins:
+![image](/uploads/49dc33170d90c0ca9815c10bd6deff00/image.png)
+
+You can see the builds in the build history. You can view the build selecting it from the build history:
+
+My output looked like this:
+![image](/uploads/a4e5a7c27dd47501bef63859602726d7/image.png)
+Console output.
+
+You can also view the sonarqube scan:
+![image](/uploads/cbd494e8d7f498a8b01dd72c41ba6363/image.png)
+Link to Sonarqube scan.
 
+Now you can see the full results of the scan:
+![image](/uploads/c37f7268be6194d46644a0a89d1f7bfc/image.png)
+Sonarqube scan.
\ No newline at end of file