Update SonarCloud workflow #306
Conversation
|
🎉 Thank you for your code contribution! To guarantee the change/addition is conformant to the OCF Specification, we would like to ask you to execute OCF Conformance Testing of your change ☝️ when your work is ready to be reviewed. ℹ️ To verify your latest change (d89a437), label this PR with |
sonnar-scanner currently doesn't handle multi configuration compilation. Thus if a file is compiled multiple times (such is the case for files in the api folder) then only the first compilation of such a file is analysed. So the best we can do is enable as many features as possible and compile target in such an order to get most of the code analysis (ie. compile client-server target first, so we get analysis with both OC_CLIENT and OC_SERVER defined)
Danielius1922
force-pushed
the
adam/bugfix/fix-sc-job
branch
from
d89a437 to
fa69b0b
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
|
Hi Daniel, This patch looks reasonable to me, so merge this patch please. |
You need to give an Approve! :D Otherwise the merge is blocked. Go to the Files Changed tab, click on the "Review Changes" button and select Approve. |
sonnar-scanner currently doesn't handle multi configuration
compilation. Thus if a file is compiled multiple times (such is
the case for files in the api folder) then only the first
compilation of such a file is analysed. So the best we can do
is enable as many features as possible and compile target in
such an order to get most of the code analysis (ie. compile
client-server target first, so we get analysis with both
OC_CLIENT and OC_SERVER defined)