sonarqube-scan

I can see line based SCM blame information in UI, but where is it stored and how can I retrieve through web API? I am using Perforce plugin. The issue is that the Perforce plugin finds the blame information from history, and because of that if a user has created a debt in a past branch, it still shows on his name in the current branch analysis. The Perforce plugin does not have any such way to disable looking into history beyond the current branch. I need to find another way to find out, if the debt is really introduced in this branch or not. The real question here is how to find out this: I

I have set up SonarQube, Maven and Cobertura to upload unit test coverage at every build run. I want to use the differential views to get coverage for the delta (new code only). The coverage itself is successfully uploaded, and I can see the delta in lines of code. However, I can't get the "Coverage on new Code" to work. I tried different values for the leak period, including previous_analysis and previous_version (changing the version from 1.0 to 1.1 in the new analysis). I also used -Dsonar.projectDate to simulate a past date of analysis but still no luck. Any thoughts? The key requirement

I am running an analysis using msbuild on debian, using the following command: mono /msbuild/SonarQube.Scanner.MSBuild.exe begin /d:sonar.login=<sonarqubetoken> /d:sonar.host.url=https://<my-server> /d:sonar.exclusions=test/**/* /k:<my-project-key> However in the end command: INFO: Index files INFO: Excluded sources: INFO: test/**/* INFO: 17 files indexed INFO: 0 files ignored because of inclusion/exclusion patterns INFO: Quality profile for cs: Sonar way INFO: Excluded sources for coverage: INFO: test/** and the analysis on the UI of my server includes files from test/ folder. Why does it

We recently started using SonarQube . We have found some rules that are suggested by SonarQube but we want to ignore them or give them a low priority and even configure the time suggested by SonarQube. For e.g We want to avoid the rule (and/or configure the priority and time suggested by SonarQube) for Document this public class. and Complete the task associated to this TODO comment. I couldn’t find a way to configure this rules to be ignored. We want this kind of rules to be ignored for the whole project not specific classes. Configuring this values would help us to have a better time

Which are the key differences between these preview and issues modes of SonarQube (greater than 5.2) analysis? Considering http://docs.sonarqube.org/display/SONAR/Concepts the main differences between publish and preview is that preview reports only issues (no measures) and no report is pushed back to the SonarQube server; this idea is clear. But what about issues ? It is written that issues is the same as preview , but should be used only for tools development. I'm a little confused, what do they mean by tools? The theory is that preview mode is what a end user should use for example when

Does SonarQube scanner support BlueOcean pipeline plugin without maven and docker, if it does how does the script works in Jenkinsfile? I'm new to Jenkins and BlueOcean and have tried all the basic possible aspects available. If the SonarQube plugin did support Declarative: pipeline { agent any stages { stage('SonarQube analysis') { tools { sonarQube 'SonarQube Scanner 2.8' } steps { withSonarQubeEnv('SonarQube Scanner') { sh 'sonar-scanner' } } } } } We cannot say that the SonarQube scanner supports or does not support BlueOcean . BlueOcean is a presentation layer which displays data provided

In our organization, we are using SonarQube 5.6 with C# plugin 5.3.1 and every issue we mark as Won't Fix gets reopened next time analysis runs. Sometimes, when the analysis runs again the issues get marked as Won't Fix (as manually marked before). We are trapped in a circle. Any ideas? 来源： https://stackoverflow.com/questions/38794909/why-does-sonarqube-reopen-issues-marked-as-wont-fix

I've been doing some research on it. What I found is a list of quite nice samples but for other languages here . I also looked at sonar-dotnet . But it doesn't look similar to the other implementations. Finally, and to be honest probably my last chance, I took a quick look at FxCop Custom Rules and I'm not sure what would be the right way. What I'm trying to do is just a basic c# rule that can be reviewed like this predefined by sonar . I mean, with Noncompliant Code and Compliant Solution . The sonar-custom-rules-examples you pointed at are all written in Java and use parsers written in Java