New code detection merge/pull requests

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

@searler

• what are you trying to achieve
  Define a baseline for main branch that future merge/pull requests are compared to

In fact, merge/pull requests are compared to the branch being targeted. There’s not necessarily a need to establish a “baseline for main branch” here.

@searler

Merged the changes to mainline, SonarQube indicated success but I noticed that also said there was no code in the project

Can you share the full analysis log?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

@searler

Without the sonar.inclusions exhaustive list the scanner claimed that there was no source code to scan and I missed that prior to the merge
NB, I have a feeling that the combination of sonar.inclusions and sonar.exclusions means that I can’t exclude code files because the inclusions overrides the exclusions

Well… Generally I would not want to start out with the analysis properties you have. Do you really have tests full comingled with source code as indicated by your analysis properties? Is there no way to point concisely to your test directories? It seems to me that you might be able to simply specify

sonar.sources=dir1, dir2,dir3
sonar.tests=common,dir1/UnitTests,dir2/UnitTests,dir3/UnitTests,dir1/unit_tests,dir2/unit_tests,dir3/unit_tests
sonar.exclusions=dir1/UnitTests,dir2/UnitTests,dir3/UnitTests,dir1/unit_tests,dir2/unit_tests,dir3/unit_tests

And BTW, I don’t think this:

@searler

sonar.cfamily.variants.names=dir2,dir3

is doing what you think it is.

 
Ann