{"id":1312,"date":"2016-09-26T10:00:20","date_gmt":"2016-09-26T08:00:20","guid":{"rendered":"https:\/\/www.nico-maas.de\/?p=1312"},"modified":"2017-01-16T21:25:53","modified_gmt":"2017-01-16T20:25:53","slug":"docker-sonarqube-with-gogsdrone-to-check-software-quality","status":"publish","type":"post","link":"https:\/\/www.nico-maas.de\/?p=1312","title":{"rendered":"[Docker] Sonarqube with Gogs\/Drone to check software quality"},"content":{"rendered":"

Sonarqube is an really useful tool to check for different kind of errors in all kinds of programming languages. If you want to check out Sonarqube in a livedemo, just go over to https:\/\/sonarqube.com\/<\/a>. In the last two parts of my Docker series we created an gogs Git Repo<\/a> as docker container and then went over to integrating gogs with drone (Version 0.4), an CI Build Server<\/a> - also as Docker container. Today, we want to install Sonarqube as a tool to check upon our software quality, so that - as soon as we push an update to our gogs project, drone will execute an analysis using Sonarqube - which will give us information about different kind of errors and code quality.<\/p>\n

# We will start by creating the needed folders:
\nsudo mkdir \/var\/sonarqube
\nsudo mkdir \/var\/sonarqube\/data
\nsudo mkdir \/var\/sonarqube\/extensions
\nsudo chown -R yourusername:yourusername \/var\/sonarqube
\n# Then we change our drone docker-compose.yml, so that drone and sonarqube will be started at the same time<\/p>\n

sonarqube:\r\n  restart: unless-stopped\r\n  image: sonarqube:lts-alpine\r\n  volumes:\r\n    - \/var\/sonarqube\/data:\/opt\/sonarqube\/data\r\n    - \/var\/sonarqube\/extensions:\/opt\/sonarqube\/extensions\r\n  environment:\r\n    - SONARQUBE_HOME=\/opt\/sonarqube\r\n    - SONARQUBE_JDBC_USERNAME=sonar\r\n    - SONARQUBE_JDBC_PASSWORD=sonar\r\n    - SONARQUBE_JDBC_URL=\r\n  ports:\r\n    - \"9000:9000\"\r\n    - \"9092:9092\"\r\ndrone:\r\n  restart: unless-stopped\r\n  image: drone\/drone:0.4.2\r\n  volumes:\r\n    - \/var\/drone:\/var\/lib\/drone\r\n    - \/var\/run\/docker.sock:\/var\/run\/docker.sock\r\n  env_file:\r\n    - .\/dronerc\r\n  ports:\r\n    - \"8000:8000\"\r\n  links:\r\n    - sonarqube<\/pre>\n
After that, we can start the service with docker-compose up -d and see Sonarqube on http:\/\/IPADDRESS:9000 (needs some time to load...).
\nTo do an check of i.e. an Java Project, we need to write an new pom.xml file:<\/p>\n
<project xmlns=\"http:\/\/maven.apache.org\/POM\/4.0.0\" xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\r\n  xsi:schemaLocation=\"http:\/\/maven.apache.org\/POM\/4.0.0 http:\/\/maven.apache.org\/xsd\/maven-4.0.0.xsd\">\r\n  <modelVersion>4.0.0<\/modelVersion>\r\n\r\n  <groupId>com.example.appexample<\/groupId>\r\n  <artifactId>appexample<\/artifactId>\r\n  <version>1.0<\/version>\r\n\r\n  <name>phpTest<\/name>\r\n\r\n  <properties>\r\n    <project.build.sourceEncoding>UTF-8<\/project.build.sourceEncoding>\r\n    <sonar.language>java<\/sonar.language>\r\n    <sonar.sources>src<\/sonar.sources>\r\n    <sonar.exclusions>src\/test\/test.php, src\/test\/test\/*<\/sonar.exclusions>\r\n  <\/properties>\r\n\r\n<\/project><\/pre>\n
and we need a new .drone.yml<\/p>\n
cache:\r\n  mount:\r\n    - \/drone\/.m2\r\nbuild:\r\n  main:\r\n    image: maven:3-jdk-8-onbuild\r\n    commands:\r\n      - mvn sonar:sonar -Dsonar.host.url=http:\/\/IPOFTHESONARQUBESERVER:9000 -Dmaven.repo.local=\/drone\/.m2\r\n      - echo \"Sonarqube has been completed.\"\r\n      - mvn clean install -Pcoverage -Dmaven.repo.local=\/drone\/.m2\r\n      - mvn package -Dmaven.repo.local=\/drone\/.m2\r\n      - mvn test -Dmaven.repo.local=\/drone\/.m2\r\n      - echo \"Build has been completed.\"\r\ndebug: true<\/pre>\n
And thats it :). Login into drone, activate your repo as valid CI repo and after that - with every push to that gogs repo, a new sonarqube analysis should be performed.<\/p>\n