[NEW RELEASE] Sonar Rust Plugin 0.0.4

I’m pleased to request inclusion of the sonar-rust-plugin 0.0.4.
It provides ability to scan Rust source code, import Clippy lints and coverage reports with LCOV or Cobertura formats

Release note : Release sonar-rust v0.0.4 · elegoff/sonar-rust · GitHub
Link to binary: https://github.com/elegoff/sonar-rust/releases/download/v0.0.4/sonar-rust-plugin-0.0.4.jar
Project site: GitHub - elegoff/sonar-rust: SonarQube plugin to analyze Rust files
SonarCloud Quality Gate: https://sonarcloud.io/dashboard?id=elegoff_sonar-rust
Link to the sonar-update-center-properties pull request : request sonar-rust inclusion to marketplace by elegoff · Pull Request #224 · SonarSource/sonar-update-center-properties · GitHub

Please note that the plugin should be added to the Plugin Library page

1 Like

Hi,

Congrats on your plugin. So you know, your request is in queue behind this one, which I’m already frightfully, embarrassingly late in getting to. So it may take a while to get to yours but I’ll do it eventually.

 
Ann

1 Like

Hi,

I’ve had a chance to start looking at this.

I’ve left a few comments on your PR but a bigger change is needed. Your plugin key (i.e. the name of the file) can’t simply be the name of a language. In fact, “rust” is specifically listed as a “don’t do” example for choosing a plugin key. :joy: Since you import Clippy lint reports, maybe rustclippy? Or communityrust? Or…

The rest of the bureaucratic requirements look good except for number 9, which I’ll look at when I do my testing.

Also, can you point me to a project to test with? Hopefully one that already has a Clippy report available?

Even before running an analysis, I see in the interface that you’ve added the Rust language and registered the file extension. Cool.

You’ve also provided a default profile but there are no rules, so the profile is empty. This is really weird.

I guess you’re importing the Clippy issues as external issues…? Is this something you plan to change in the future? Because as-is I have to wonder why you’re declaring the language and not just providing a pure utility to import Clippy issues (on unrecognized files). I guess you’ve declared the language so you can also import coverage data? If so… I think I’m going to have to hold out for a non-empty default profile. :woman_shrugging:

 
Ann