Hi @Abbas,
Why not do the static analysis and the coverage with the with x64-Debug flavor?
The static code analysis is already performed on the x64-Release. This is the code that gets shipped to the customers, while the Debug flavour is only used internally for development & debugging purposes.
In any case, given the answers received so far - we will have to do both static analysis and code coverage for x64-Debug, despite the fact that it might slow down a bit the PR workflow.
If for some reason you don’t want to do that and you are using CMake, you can generate the compilation database of x64-Release without building and combine it with the coverage from the
x64-Debug.
This is exactly what we’re already doing for x64-Release: generating the compilation database without actually building. What do you mean by combine? As far as I know it’s not possible to combine multiple reports into a single report / project (according to SonarCFamily - Compile same code base with several compilers - #2 by mpaladin). Due to the linked issue, w have up to 9 Sonar projects for a single repo (Linux x64, macOS x64/arm64, Windows x86/x64/arm64/, plus 3 more projects for CodeCoverage) 
.
I have the feeling the original question on this thread is being lost: is it possible to publish LLVM Code Coverage reports on Windows that were generated using the clang-cl.exe compiler (and also using sonar.cfamily.compile-commands to specify the path to compile_commands.json)?
Thanks.