Setting up SonarQube

Now that we can run our Gulp tasks and trigger a build automatically on commit, it is time to add the next step towards quality code, SonarQube. We have already installed, configured, and used SonarQube in Chapter 2, Setting Up a CI Environment, so I assume you have it ready for use. If things do not work, be sure to review Chapter 2, Setting Up a CI Environment, and the part on SonarQube in particular. Here is a little reminder: SonarQube is accessible on ciserver:9000. So, go to your project configuration and add the Execute SonarQube Scanner build step. Put the following configuration in the Analysis Properties field:

sonar.projectKey=chapter7sonar.projectName=Chapter 7sonar.projectVersion=1.0sonar.sources=.sonar.exclusions=node_modules/**, ...

Get Continuous Integration, Delivery, and Deployment now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.