Elixir projects in SonarQube

What’s a sonar cube ?

Well it seems that is a tool for Continuous Code Quality, first time I come across it…

@b3k What issues did you encounter using

See business proposition Q7: why YOUR business needs SonarQube.

Any update on this?

GitHub - peterquicken/sonar-elixir: SonarQube Elixir plugin · GitHub fork seems to have had some activity

Thanks, I will check that fork

It has only basic support (LoC, module counting), without any code rules like code smells etc, from my organization perspective its kind important thing.

Same here. It’s not even considered if there is no sonarqube support.

Is not possible to integrate Credo with Sonar?

I’ve tried to make it work with some duct tape!

Here is the plugin:

• https://github.com/adrienmo/sonar-elixir/releases/download/1.0/sonar-elixir-plugin-1.0-SNAPSHOT.jar

Which I just found out there and compiled, basically it just give you the ability to scan .ex and .exs files.

Then I extended elixir existing tools to create generic reports:

• generic code coverage: I made a pull request that was accepted by the library: GitHub - parroty/excoveralls: Coverage report tool for Elixir with coveralls.io integration. · GitHub, you can generate the report with: “mix excoveralls.xml”
• generic issues: I made a plugin for credo GitHub - adrienmo/credo_sonarqube: Add option to credo to generate sonarqube generic issue file · GitHub
• generic test execution: I made an ExUnit formatter: GitHub - adrienmo/ex_unit_sonarqube: Generate a generic test execution file to be used with SonarQube · GitHub

You then need to configure your:

• sonar.externalIssuesReportPaths
• sonar.coverageReportPaths
• sonar.testExecutionReportPaths

accordingly.

Coverage and execution works fine, credo plugin need some work to classify correctly bug/codesmell/vulnerability and time effort (right now it reports everything as code smell with 90 minutes time resolution) but it works

Hope it helps!