SonarGo coverage not scanning Go files that are in the sonar server

go

(Kevin Cheng) #1

Hi Sonar Community,

My team is trying to analyze Golang files with SonarGo. We are using the mvn-golang plugin (https://github.com/raydac/mvn-golang), the maven scanner version is 3.4.1.1168, SonarQube is version 6.7.4, and SonarGo is 1.1.0.
I see the files I want to scan are showing up at the sonar server, however, when I try to load the coverage report, I get warnings telling me the file “is not included in the project, ignoring coverage”.
Please let me know if I need to provide any other information! Thanks!!

Best,
Kevin


(Tibor Blenessy) #2

Hello,

can you post your analysis logs and structure of your project? Also if you can include the coverage report. I am not familiar with mvn-golang plugin, try to run with -X option so we have more logs.


(Kevin Cheng) #3

Hi Tibor,

Sure, there a tons of logs and I’m not totally sure if this is what you’re looking for, so please tell me if I should send more:
Here are my analysis logs:
Analysis Logs.txt (8.3 KB)

The structure of my project is ecdm/adm/adm-agent-core/src/myCompany.com/, and i have several directories within /myCompany.com/ with golang files I want to scan.

And here is a few lines of the coverage report (in total, the original is around 30.5k lines):
Partial Coverage Report.txt (2.3 KB)

I’m not sure if I’ve given you enough info, so please let me know if it’s not enough or if you need anything else, thank you!


(Dan Tran) #4

This is same as https://github.com/SonarSource/sonar-go/issues/218


(Tibor Blenessy) #5

Please let’s keep discussion in one place, preferably here, otherwise is difficult to collect all the information. Also don’t comment on closed issues.

Would it be possible for you to create small example repository repository reproducing the issue? You can also use https://sonarcloud.io to do the analysis.


(Dan Tran) #6

per GitHub issue, the solution is to setup the GOPATH before running the scanner


(Kevin Cheng) #7

Thanks for your time Tibor! We have resolved our issue with how Dan described