-
Notifications
You must be signed in to change notification settings - Fork 13
Installation
In order to use this plugin on your SonarQube server instance, you need first to install it.
Installation of official releases of the plugin couldn't be simpler: the plugin is available in SonarQube's update center under the name "Code Smells". Just search for the plugin, install it, restart yourSonarQube instance and that's it!
Release Candidate (RC) versions can be directly downloaded from the project's GitHub releases page. If you want to install a RC version or a SNAPSHOT version built from source, you have to follow these steps:
- Download the RC version of the plugin / or build a SNAPSHOT version of the plugin
- Stop your SonarQube instance
- Remove any previously installed version of SVG Badges from
<sonarqube_root_directory>/extensions/plugins
- Copy the new version of the plugin to
<sonarqube_root_directory>/extensions/plugins
- Start your SonarQube instance
In order to have the plugin detect the various Smells types, and have Smell annotations appear as violations which contribute to the project's technical debt, you need to add to your profile all rules part of the Smells
rules repository.
Note 1: While I recommend activating all rules part of the Smell
repository, you don't have to do it. If the rules are not activated, the plugin will still report Smell related technical debt in its own widget, but Smell annotations will not be counted as issues, and as such they will not contribute to the project's technical debt, nor impact the SQALE rating. Do this if you don't want to mix automated debt discovery with "subjective" debt declaration.
Note 2: If you decide to activate Smell
rules in your profile, make sure to activate all of them, otherwise, only those that have been activated will appear as issues.
When using SonarQube < 6.0, you can add the Code Smells
widget to your project or view dashboard.