In continuation of the above thread, I have doubts with managing the coverage reports for our code base, as mentioned previously that our build depends on different targets so the coverage reports will also be different.
Now, the third party tools that are mentioned in the sonar documentation follows dynamic approach for coverage.xml reports as at some point we have to debug(referring to Gcovr). But we are looking for something that could provide it without debugging and follows static approach.
Is this about finding a coverage tool that will measure coverage across all your build configurations at once, regardless of what directives are enabled / disabled? If so, that’s out of scope for us.
yes, I asked about that only.
I am aware that sonarqube doesn’t have a smooth packaged procedure for code base that requires different builds based on different targets that’s why I’m going with creating various branches like master branch under one project on sonarqube.
can you tell me the how does the output varies in sonarqube if the build is showing some fatal errors but I am able to perform sonar-scanner analysis after that with success execution.