Hi everyone,
Actually I am Analyzing projects .net framework with GitHub Actions.
I have a problem using the sonar-scanner-9.0.0.100868-net-framework client, this in order to analyze a .net framework 4.8 code, the CS lines of code are not analyzed and only duplicate code is displayed:
I share the logs of the analysis performed:
logs_30954215876.zip (59.4 KB)
Is something missing in the configuration the solution NET?
Thanks.
Hi Edwin,
Welcome to our community!
I checked the logs and from what I can see, although 14 projects are detected, the analyzers do not raise any issues. I would need more details to understand why. Would it be possible to share with us the logs in the verbose mode? You can enable verbose mode by using /d:sonar.verbose=true parameter when calling the scanner begin command.
Hi Edwin,
Thanks for sharing the logs with us. I took a look and the problem is not obvious. We need to investigate further.
Hi Edwin,
Would it be possible to share the dotnet build logs in the binary format? You can generate the binary format by providing the -bl: parameter like so: dotnet build --no-incremental -nr:false -bl:build.binlog.
This will give us more insight into why the analyzers are not properly linked and executed during the build.
Hi Costin,
I attached log with command:
msbuild.exe DAV_MULTIVENDOR.sln -nologo -nr:false -p:DeployOnBuild=true -p:DeployDefaultTarget=WebPublish -p:WebPublishMethod=FileSystem -p:DeleteExistingFiles=True -p:configuration=Debug -p:UseAppHost=false -bl:build.binlog -t:Rebuild
Thanks.
logs_31184684861.zip (624.4 KB)
Hi Edwin, I cannot find the build.binlog file in the archive.
Hi,
I’m sorry to get back to you and ask for more logs, but could you please share with us the .sonarqube folder generated after the project has been built?
For the run we have logs, it was generated to D:\a\davi-atm-multiservicios-mngr\davi-atm-multiservicios-mngr\NET\DAV_MULTIVENDOR\.sonarqube.
When checking the logs everything looks fine: the projects are categorized as MAIN code categorized as MAIN project (production code), the files are found for analysis Number of files to analyse: 70. and the analyzers are passed to the compiler /analyzer:...\SonarAnalyzer.CSharp.dll. At the same time, there are no sonar warnings raised and there are no lines of code reported, which means that the analyzers were not executed.
HI Costin,
Do you have any update?
Thanks,
Edwin
Hi Edwin,
I was caught up with other tasks, and only now I found some time to take a look. From what I can see, the analyzer that is responsible for computing metrics was executed, but it generated data only for just a few files (like SharedAssemblyInfo.cs).
One reason this might happen is if the analyzer detects that the code is generated. Are any of the following attributes used in the code files?
Or, do the files (maybe the headers) contain comments with the following strings:
Any of these criteria might make the analyzer think that it’s analyzing generated code, which would lead to skipping the analysis.
One thing you might try (just for a test) is to enable generated code analysis
Just to double-check. Have you re-done the code analysis after the setting was enabled?
Hi Costin,
Yes, We done code analys after the settings those values.
Thanks.
Edwin
Hey there @edwin-avila_davicode !
I took a look at your problem as well and discussed it a bit with my colleague.
The reason this behavior is happening is because we are considering your analysis as an Incremental PR analysis.
This means that we are not analyzing all the files, but only the ones that have changed between the PR branch and the base branch. This happens for performance, so that the scan is faster, as a full-scan has to look into more finals and generate issues and metadata.
We noticed that it is not currently possible to disable this, so I made a ticket where you can track the effort.
What I am curious about is why you can see the files in the screenshot at all.
If the analysis is working as intended, then the files should not appear at the browser.
I have a couple of follow up questions for you:
GITHUB_BASE_REF, which is a PR-exclusive environment variable.on:
push:
branches:
- master
pull_request:
branches:
- master
Hi Gregory,
Sorry for the delay in the response:
Are the logs you send us happening in a PR? R/ Yes, these logs come from a PR, this pull request start YML secuence:
Build command:
msbuild.exe DAV_MULTIVENDOR.sln -nologo -nr:false -p:DeployOnBuild=true -p:DeployDefaultTarget=WebPublish -p:WebPublishMethod=FileSystem -p:DeleteExistingFiles=True -p:UseAppHost=false
I cannot share you the SONAR URL because you don’t have access. I send you the Sonar Analisis code screenshot:
Thank you a lot for you help.
Regards,
Edwin
It’s funny you say that, because I went back to the first set of logs you shared and noticed that your scanner command explicitly sets sonar.branch.name.
2024-11-15T21:37:51.4497513Z + SonarScanner.MSBuild.exe begin /key:davi-atm-multiservicios-mngr /name:davi-atm-multiservicios-mngr /organization:davivienda-colombia -d:sonar.host.url=https://sonarcloud.io -d:sonar.login=*** -d:sonar.branch.name=integration -d:sonar.dotnet.excludeTestProjects=true
So what’s probably happening is that:
sonar.branch.name=integration, resulting in a branch analysis (rather than a PR analysis)The answer here is probably as simple as removing sonar.branch.name from your scanner command and letting the scanner auto-detect whether it should be analyzed as a PR or as a branch.
If you really want to preserve a branch analysis of the integration branch (to see the full results, not just what changed in a PR) , you could add integration to the branches you list under on: push: branches: of your GitHub Actions YML.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.