Sonar6.0 application part 5: Sonar web analysis configuration

First, exclude code directories and files that do not need to be scanned

1. Log in to Sonar as an administrator and enter the configuration-- "General Settings--" exclude-- excluded source files.

Second, the language code scanning rules required for installation

1. Enter the configuration-"system -" Update Center-"Available"

2. The rules for vulnerabilities, violations, and BUG scanning for Jave development can be as follows

Configure code scanning rules

1. Enter the configuration-"General Settings -" Java, JaveScript, SCM, and technical debt to modify as needed. Generally, you can do so by default.

Fourth, quality configuration, setting default scanning rules for each language

Fifth, code rule setting

If you think that some scanning rules are too strict, you can "suspend" them, and later built code will no longer use this rule when scanning the project, such as suspending a BUG rule in JP:

You need to set the severity of the rule when you activate the code

Click the active rule name to set the severity level of the rule

VI. Allocation indicators

1. Modify a filter for dashboard display

Modify column

Add the most commonly used columns

2. Set up a private filter to display the file name where BUG is located

Copy a filter before configuring it

Set indicators in "more conditions"

7. Configure the dashboard

Change the name of the dashboard

Enter the dashboard configuration interface

Sample dashboard that has been configured