You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: After upgrading SonarQube, reset the quality profile for the languages which use Coverity
46
42
(in **Quality Profiles**, select **Restore Built-in Profiles**, and select the language.)
47
43
48
-
Configuring the Coverity Sonar Plug-in
49
-
======================================
44
+
## Configuring the Coverity Sonar Plug-in
45
+
-----------------------------------------
50
46
51
-
Once installed, you must configure the Coverity Sonar plug-in for
52
-
general use.
47
+
Once installed, you must configure the Coverity Sonar plug-in for general use.
53
48
54
49
1. Log in to SonarQube as an administrator.
55
50
@@ -66,8 +61,8 @@ general use.
66
61
6. Click **Save Coverity Settings** to complete the
67
62
basic configuration.
68
63
69
-
Configuring your Project Settings
70
-
=================================
64
+
## Configuring your Project Settings
65
+
------------------------------------
71
66
72
67
After configuring the general plug-in settings, you must select the
73
68
correct Coverity Connect project to associate with each of your Sonar
@@ -100,8 +95,8 @@ whenever you run SonarQube Scanner on the specified project. This
100
95
configuration must be completed for each project you wish to link with
101
96
Coverity Connect.
102
97
103
-
Setting Up sonar-project.properties
104
-
===================================
98
+
## Setting Up sonar-project.properties
99
+
--------------------------------------
105
100
106
101
For the plug-in to successfully display Coverity defects, the correct
107
102
source paths must be entered in the sonar-project.properties file at the
@@ -157,12 +152,12 @@ See below for a complete example sonar-project.properties file.
157
152
>
158
153
> \# sonar.coverity.prefix=MyOptionalPrefix
159
154
160
-
*Note*: When using the Coverity plug-in, use the language key "cov-cpp" instead of "c", "c++", or "cpp". This language key prevents conflicts with non_Coverity plug-ins.
155
+
*Note*: When using the Coverity plug-in, use the language key "cov-cpp" instead of "c", "c++", or "cpp". This language key prevents conflicts with non-Coverity plug-ins.
161
156
162
157
To specify the language key:
163
-
-Add "sonar.language=cov-cpp" (or another preferred language) to the properties file.
-Make sure that **Administration >Configuration> Languages** and your project level settings (**Project Settings > General Settings > Languages**) don't contain the suffixes that you configured above to avoid conflicts. For example, if your Coverity language configuration includes <code>\*\*./\*.cpp </code>, make sure to remove <code>\*\*./\*.cpp </code> everywhere else.
160
+
-See https://community.sonarsource.com/t/language-of-file-dal-db2-vb-can-not-be-decided-as-the-file-matches-patterns-of-2-languages/21998 and https://community.sonarsource.com/t/language-of-file-can-not-be-decided-as-the-file-matches-patterns/16246 to see example conflicts.
166
161
167
162
*Note*: The "sonar.coverity.prefix" property is used to help locate files when anlyzing with the sonar scanner. The prefix value will be removed from the "File path" value on the Coverity Connect issue.
168
163
- the value must match exactly, if having trouble finding the source files look at the Coverity Connect issues "File" column
@@ -174,8 +169,7 @@ To specify the language key:
174
169
- If **sonar.coverity.stream** is not configured, then the plugin will use **sonar.coverity.project** to fetch defects from.
175
170
176
171
177
-
The Coverity Widget
178
-
===================
172
+
# The Coverity Widget
179
173
180
174
The Coverity plug-in includes a Coverity widget that displays
181
175
Coverity-specific measures. The Coverity widget is available with SonarQube versions before version 6.2.
@@ -192,17 +186,15 @@ Coverity-specific measures. The Coverity widget is available with SonarQube vers
192
186
- The Coverity widget can be added to the Dashboard by two different routes: as Admin,
193
187
go to **Dashboards > Manage dashboards**, or in a Project, go to **Dashboard** and add it there.
194
188
195
-
Sonar Scanner with SSL
196
-
===================
189
+
# Sonar Scanner with SSL
197
190
198
191
Coverity SonarQube Plugin provides a connection to Coverity Connect through SSL. The certificates should be imported to the java key chain where Sonar Scanner is running from.
199
192
200
193
Sonar Scanner provides its own jre bundle as part of Sonar Scanner. This means that if a user installed java locally, the certificates need to be imported to the jre which is bundled with Sonar Scanner.
0 commit comments