SonarQube not excluding a specific rule Ask

[sandeep manthri]

I've posted the same question on stackoverflow but haven't got any response hence reposting it here. Link to original post https://stackoverflow.com/questions/49849879/sonarqube-not-excluding-a-specific-rule

We are trying to suppress a couple of specific rules: csharpsquid:S3990 & csharpsquid:S4041 from analysis, we can see that the rule csharpsquid:S4041 is being excluded but violations\issues for csharpsquid:S3990 are still being shown in analysis report.

Format given, Rule Key Pattern : csharpsquid:S3990 File Path pattern : **/*.*

Csharp plugin version: 7.0.1 (build 4822) SonarQube version: 6.7.1

We run analysis from Sonarqube VSTS tasks.

Has anyone else faced this or is it something specific about the rule that it cannot be suppressed?

Also can we enforce SonarQube to use a specific ruleset for analysis instead of default SonarQube ruleset?

[G. Ann Campbell]

Hi,

At what level are these issues being raised? I'm thinking it's ... at directory level?

Regarding profiles, there are 2 different things you might be asking:

* How do we use a profile other than the Built-in ones?

Create a new profile and make it the Default.

* How do we analyze a project with a profile that's not the Default (as distinct from the Built-in profiles which may or may not be the defaults)

Explicitly assign your project to your non-default profile. This can be done either from the profile side or from the project side.

Ann