sonarqube-scan

SonarQube MSBuild fails to exclude files

这一生的挚爱 提交于 2019-12-31 04:43:09
问题 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:

Why does SonarQube reopen issues marked as Won't Fix?

心不动则不痛 提交于 2019-12-30 09:52:09
问题 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

Why is Gradle / / Sonar Jacoco looking for dir and also project?

戏子无情 提交于 2019-12-25 08:47:31
问题 Background: We have two subprojects each with many sub-sub-projects. The root project is an empty parent. We have one project that is strictly for the flyway plugin. Often times names do not match directories. For perspective, settings.gradle is 219 lines and roughly half of those are projects. So I'm getting this error: Caused by: java.lang.IllegalStateException: The base directory of the module ':commons:sitewidget' does not exist: /dev/abc/commons/:commons:sitewidget Here is the question:

Sonarqube + Cucumber + Gradle

断了今生、忘了曾经 提交于 2019-12-25 08:14:55
问题 Whenever I try to run ./gradlew sonarqube I get the following message: Scenario: This is a test # sample/helloworld/readycheck.feature:3 Given This is my first step # StepDefinitions.This_is_my_first_step() When This is my second step # StepDefinitions.This_is_my_second_step() Then This is my third step # StepDefinitions.This_is_my_third_step() 1 Scenarios (1 passed) 3 Steps (3 passed) 0m0.221s sample.helloworld.ReadyCheckTest > testDoGet STANDARD_OUT Checking ready status... Returing ready

SonarQube 5.6 FileNotFound exception during AST Scan

天涯浪子 提交于 2019-12-25 08:07:12
问题 During the AST Scan, I get a FileNotFoundException looking for a symbols-34.pb file: ERROR: Error during SonarQube Scanner execution org.sonar.squidbridge.api.AnalysisException: SonarQube is unable to analyze file : '/workingDir/src/main/java/package/JavaFile.java' at org.sonar.java.ast.JavaAstScanner.simpleScan(JavaAstScanner.java:93) at org.sonar.java.ast.JavaAstScanner.scan(JavaAstScanner.java:67) at org.sonar.java.JavaSquid.scanSources(JavaSquid.java:133) at org.sonar.java.JavaSquid.scan

SonarQube scanner: use non-default Java

旧时模样 提交于 2019-12-25 07:27:54
问题 I have a box running SonarQube scanner. The default JDK is 7. I need to run sonar-runner using JDK 8 but I would like to keep the default JDK at 7. I tried changing JAVA_HOME before running sonar-runner but had no luck. I also couldn't find any properties that can change that. Any thoughts? 回答1: Setting JAVA_HOME should work (see sonar-scanner source code if you're curious). It's behaving well for me with SonarQube Scanner 2.6.1. Default on Java 7: nico@deb-nico:~$ sonar-scanner INFO: Scanner

Sonarqube producing different results in different folders

微笑、不失礼 提交于 2019-12-24 18:45:42
问题 Update 1: It is actually not related to the build server, I have checkout my repo into a fresh folder and can observe the same behavior so it definitely isn't a version problem. I have compared the .sonarqube folders and cannot see anything unusual. What could be causing the results from one csproj to be ignored when building from another location? Original question: I'm setting up sonarqube for a .net project (1 .sln, 2 .csproj), when I run the analysis on my machine it works, all the files

Sonarqube 5.6.3 reopens issue marked as won't fix

浪尽此生 提交于 2019-12-24 10:16:09
问题 we are using SonarQube version 5.6.3 and it is installed on linux server( CentOS release 6.8 ). Even after marking issue as "Won't Fix" manually, the issue seems to get open after another analysis in jenkins ( Jenkins ver. 1.642.3 ) . Out of many engagements (appprox. 100+), One engagement holds its project snapshot from August 2015 to till date. I was thinking of deleting the snapshot, but engagement wants an another alternative. I am not sure what is causing this issue. Does anyone has the

SonarQube: Scanning process ignores lcov.info

孤者浪人 提交于 2019-12-24 09:09:11
问题 I am scanning a ui project. The source code is in typescript . gulp test-coverage generates .js files (which are then scanned for coverage). (each .ts file gets a .js file right next to it, in the same location) I am pointing the scanner to the lcov.info file as follows: sonar.javascript.lcov.reportPaths=test-coverage/lcov.info The problem : The lcov.info , provides coverage information for .js files For some reason, SonarQube also provides coverage information for the *.ts files (although

Sonarqube support for ‘.Net Core’ (with .xproj extention) projects

雨燕双飞 提交于 2019-12-23 20:29:22
问题 Anyone has any idea on whether ‘.Net Core’ (with .xproj extention) projects are supported by Sonarqube v4.x or v5.x (C# plugin version 5.2)? Though there is no error message in SonarQube Scanner log file, all our .xproj files are listed under “Skipped projects” in ProjectInfo.log file and dashboard is showing results only for .csproj files and not for any .xproj files. Thank you for the your response for this 回答1: Per documentation of the SonarQube Scanner for MSBuild (which is the scanner to