Closed josceley closed 1 year ago
Hi @josceley,
Originally SonarQube was a tool to measure Technical Debt. Technical Debt are actually code smells and less bugs. Bugs in the code are/were mostly syntax errors. How the issues are classified is described in the profiles under rules (and up to the developer of the sensor). Classical static code analysis tools (e.g. Cppcheck, ClangTidy) find rather code smalles than bugs.
Regards,
Hi @guwirth. Yes, the rules are enabled, as shown in the images below.
Division by zero in code:
Divide-by-zero bug rules enabled.
Nothing detected.
One of the three detected code smeels is related to the new lines I added, as shown in the image below.
I have another very large project that does not indicate any bugs, which confirms that the rules are not being processed.
Hi @josceley,
the rules are active, one is from Cppcheck and one from Infer.
Regards,
Hello everyone. Recently I installed the plugin version 2.1 on my sonar installation version 9.0.1 without any problems. I created a new quality gate set, enabled all the rules, and came across the following scenario: Code smell rules are parsed but Bug rules are not. That is, no bugs are reported in the projects. tested in several projects with the same symptom and in two installations of Sonar.
Below the LOG