You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue or pull request for this?
I have searched the existing issues and pull requests
Feature description
In PR #580 we introduced sonar scanning to this project. However, for now we have disabled scanning of the C files because it requires additional setup as described on https://docs.sonarsource.com/sonarcloud/advanced-setup/languages/c-family/overview/. This request is an open ticket to the community for anyone with more advanced C knowledge to set up our pipelines so Sonar can scan the C code.
Desired solution
Updates to our GitHub action workflows for having Sonar scan C code. After building the C code unit tests should also be run with yarn test so a coverage report can be analyzed.
Is there an existing issue or pull request for this?
Feature description
In PR #580 we introduced sonar scanning to this project. However, for now we have disabled scanning of the C files because it requires additional setup as described on https://docs.sonarsource.com/sonarcloud/advanced-setup/languages/c-family/overview/. This request is an open ticket to the community for anyone with more advanced C knowledge to set up our pipelines so Sonar can scan the C code.
Desired solution
Updates to our GitHub action workflows for having Sonar scan C code. After building the C code unit tests should also be run with
yarn test
so a coverage report can be analyzed.Alternatives considered
Rewriting the C code to Rust and using a tool such as https://gitlab.com/woshilapin/cargo-sonar to convert the output of Rust tooling to Sonar compatible tooling.
Additional context
No response
SFW-84
The text was updated successfully, but these errors were encountered: