Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: add a GitHub workflow to submit Coverity scans
Coverity is a static analysis tool that detects and generates reports on various security and code quality issues. It is particularly useful when diagnosing memory safety issues which may be used as part of exploiting a security vulnerability. Coverity's website provides a service that accepts "builds" (which contains the object files generated during a standard build as well as a database generated by Coverity's scan tool). This GitHub workflow performs that job when the repository variable "ENABLE_COVERITY_SCAN_FOR_BRANCHES" has been configured accordingly (see https://docs.github.com/en/actions/learn-github-actions/variables for details how to configure repository variables): It is expected to be a valid JSON array of branch strings, e.g. `["main", "next"]`. In addition, this workflow requires two repository secrets: - COVERITY_SCAN_EMAIL: the email to send the report to - COVERITY_SCAN_TOKEN: the Coverity token (look in the Project Settings tab of your Coverity project). To run the workflow on a pool other than `ubuntu-latest`, the repository variable `ENABLE_COVERITY_SCAN_FOR_OS` can be set to a valid JSON array of string, e.g. `["ubuntu-latest", "macos-latest"]`. Note: The initial version of this patch used `vapier/coverity-scan-action` to benefit from that Action's caching of the Coverity tool, which is rather large. Sadly, that Action unfortunately only supports Linux, and we want to build on Windows, too. Besides, Coverity requires `cov-configure` to be run in the meantime, and that Action was not adjusted accordingly. So it would seem to be a better way forward to carry a working set of steps than trying to rely on that Action. Initial-patch-by: Taylor Blau <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
- Loading branch information