Using SonarCloud with Travis CI
SonarCloud is a cloud service offered by SonarSource and based on SonarQube. SonarQube is a widely adopted open source platform to inspect continuously the quality of source code and detect bugs, vulnerabilities and code smells in more than 20 different languages.
Please refer to the SonarQube documentation for more details on how to configure different scanners.
You are using one of the two following environments:
- CI Environment with JVM VM image - for instance:
Inspecting code with the SonarQube Scanner #
Before inspecting your code, you need to:
- Create a user authentication token for your account on SonarCloud.
- Encrypt this token
travis encrypt abcdef0123456789or define
SONAR_TOKENin your Repository Settings
- Find which SonarCloud.io organization you want to push your project on and get its key
- Create a
sonar-project.propertiesfile for your project (see the documentation).
Then add the following lines to your
.travis.yml file to trigger the analysis:
addons: sonarcloud: organization: "sonarcloud_organization_key" # the key of the org you chose at step #3 token: secure: "*********" # encrypted value of your token script: # other script steps might be done before running the actual analysis - sonar-scanner
Please take a look at the live example project to know more about this standard use case.
SonarQube Scanner for Maven #
Lots of Java projects build with Maven. To add a SonarCloud inspection to your Maven build, add the following to your
addons: sonarcloud: organization: "sonarcloud_organization_key" # the key of the org you chose at step #3 token: secure: "*********" # encrypted value of your token script: # the following command line builds the project, runs the tests with coverage and then execute the SonarCloud analysis - mvn clean verify sonar:sonar -Pcoverage -Dsonar.projectKey=myorg_myrepo
Please note the following:
- the “coverage” profile activates the generation of the JaCoCo XML report
- “sonar.projectKey” can also be set as a property on the main POM file. Its value can be found on the right side of the project homepage on SonarCloud
Please take a look at the live Maven-based example project to know more about this use case.
Analysis of internal pull requests #
SonarCloud can inspect internal pull requests of your repository and write comments on each line where issues are found.
For security reasons, this advanced feature works only for internal pull requests. In other words, pull requests built from forks won’t be inspected.
To activate analysis on pull requests, you need to install the SonarCloud application on your GitHub organization(s).
Note that if you used SonarCloud before the GitHub application and therefore configured GitHub tokens on your projects, you should now delete those tokens from the “Administration > General Settings > Pull Requests” page of your projects.
Upcoming improvements #
Future versions of this add-on will provide the following features:
- Support for external pull requests.
Accessing full SCM history #
Travis CI uses shallow clone to speed up build times, but a truncated SCM history may cause issues when SonarCloud computes blame data. To avoid this, you can access the full SCM history with:
git: depth: false
Deprecated features #
If you are a long-time SonarCloud user, you might have the following entries in your
If this is the case, you will get warnings in the log, telling you that this behaviour will be removed soon. You should get rid of those entries in your
.travis.yml file to benefit from the latest features of SonarCloud.
Note for SonarQube users #
These properties are completely useless, the SonarCloud add-on manages them for you depending the analysis type.