Why not use Rubycritic report?

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube: 10.2.1
    Ruby plugin:

Plugin not support import analyze from rubycritic. It’s a powerfull analyzer for Ruby.
Rubycritic can export analyze in json file.

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hello Florian,

To answer your question, we don’t support the import of Rubycritic mainly because this is the first time I hear about it. So thanks for reporting this.

I’ll therefore create a card in our various portals and see if some other Ruby developers are interested. If this is the case, then we will prioritize this shortly as the ROI is very high (the cost to support a new external linter is low on our side and the value is certainly high for Rubycritic users).

Would you be able to highlight a couple of features or rules that you particularly like in Rubycritic?



Here is the portal card for SonarQube.

1 Like

Sorry for my late reply.
I think the “Code smell” feature of rubycritic can be important to integrate first. Because code smell of sonarqube is not powerfull.