HI again,
First analysis has been run.
Results can be followed here :
https://sonarqube.com/component_issues/index?id=haproxy#resolved=false|types=BUG%2CVULNERABILITY
Some rules are just best practices that you could consider irrelevant, some are indications of code that could be refactored …
Pick your favorites.
Regards,
Mildis
Le 17 juin 2016 à 18:01, Willy Tarreau <[email protected]> a écrit :
Hi Mildis,
On Thu, Jun 16, 2016 at 09:09:08PM +0200, Mildis wrote:
Hi list, Hi Willy,
At my job, we are using SonarSource???s SonarQube code analysis tool to get insights of the code health.
This tool allows to highlight defects in the code which might go under the radar of sharp developper eyes.
SonarQube is opening its platform to analyse opensource project, see https://sonarqube.com <https://sonarqube.com/>
Number of opensource project are actively analyzed, whatever the language used.
Integrating a new project in the SonarQube analysis requires the approval of the authors/maintainers of the project.
It could be interesting for HAProxy to be analyzed so ???little hands??? could help solving bugs pointed by the tool.
Do you think HAProxy could benefit this tool ?
Will you agree for HAProxy to be included in the SonarSource portal ?
Sure, as long as I'm not bugged by the tool's automatic reports :-)
Thanks,
Willy
|
