There are several ways for you to achieve this, depending on the importance you give to this duplication issue. SonarQube reports what it finds, it’s all up to you to decide what to do with it. If you believe that this is indeed an issue, you have to refactor your code: SonarQube cannot report duplication … Read more
A little information on how cognitive complexity works and why you should keep it low First of all it is important to understand how “Cognitive Complexity” works as compared to “Cyclomatic Complexity“. Cognitive complexity takes into account the complexity perceived by the human brain. This is why it does not simply indicate the number of … Read more
I believe the only syntax supported for Python (assuming it is supported) is the NOSONAR comment, so #NOSONAR or # NOSONAR at the end of the line where you want to ignore issues. Unfortunately, this is a global issue suppression: it kills all issues on the line, not just those from a specific rule.
As mentionned here : https://github.com/jacoco/jacoco/pull/513#issuecomment-293176354 filtering is performed at a time of report generation (creation of html, xml, etc), not at a time of collection of execution information (creation of exec file). So that tools that read execution data directly instead of reading of xml (which is a kind of mistake on their side to … Read more
Coverage is a subtle 😉 mix of the line and the branch coverage. You can find the formula on our metric description page: coverage = (CT + CF + LC)/(2*B + EL) where CT – branches that evaluated to “true” at least once CF – branches that evaluated to “false” at least once LC – … Read more
This is a known issue introduced with SonarJava 5.1. You can safely consider this issue as a False Positive (FP) and/or ignore it. It has already been fixed while handling JIRA ticket SONARJAVA-2633. The fix has been delivered with version 5.1.1 of SonarJava analyzer, released on Feb 16, 2018 (requires SonarQube LTS 6.7 or superior). … Read more
Since SonarQube 4.0, you can define issue exclusion patterns based on rule key and file path pattern. On previous versions, you can rely upon the Switch Off Violations plugin.
Shortly, leak period is time frame (usually since last release), where specified criteria are measured on newly added code. This allows to focus on quality of fresh code and stop the accumulation of technical debt. The “leak” concept is explained in documentation here https://docs.sonarqube.org/display/SONAR/Fixing+the+Water+Leak Update SonarSource has fleshed-out and updated the terminology / philosophy: https://sonarqube.org/features/clean-as-you-code.
First try to stop the SonarStart.bat by using Ctrl+c as suggested , and then try to open localhost:9000 ( or whichever port you configured sonar server). If it is still opening then go to task manager and search for wrapper.exe service and stop the service, if no service or app is found then goto: Task … Read more
There are several ways, one of which is adding the sonar.skip property inside the pom.xml of the project / module you want to skip. This excludes a project from SonarQube analysis: <properties> <sonar.skip>true</sonar.skip> </properties> This also works with Jenkins and running Sonar as a post build action. For more details see: Analyzing with SonarQube Scanner … Read more