Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Scan with Coverity #262

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cgzones
Copy link
Contributor

@cgzones cgzones commented Aug 25, 2020

This is an attempt to revive Coverity Scan.

Please do not merge but instead push to the branch coverity_scan and replace the secure token with a value from
https://scan.coverity.com/projects/selinuxproject-selinux/builds/new?tab=travis_ci -> Example

Signed-off-by: Christian Göttsche <[email protected]>
@cgzones cgzones closed this Jan 6, 2021
@cgzones cgzones deleted the coverity_scan branch January 6, 2021 12:26
@evverx
Copy link
Contributor

evverx commented Nov 16, 2021

@fishilico could you add a secret named COVERITY_SCAN_TOKEN to the repository? I'll try to add an action sending data to Coverity daily by analogy with util-linux/util-linux#1491.

@cgzones cgzones restored the coverity_scan branch November 16, 2021 10:10
@cgzones cgzones reopened this Nov 16, 2021
@evverx
Copy link
Contributor

evverx commented Nov 16, 2021

In the meantime, I think another option would be to set up codeql. I kind of integrated it into my fork in evverx#1 and it seems to be working
Screenshot 2021-11-16 at 16 14 45

I'll try to polish it a bit and open a PR here

The downside is that all the alerts are hidden in the security tab of repositories, which makes it hard to keep track of reports in one place for external contributors. On the other hand, once codeql ends up in forks they are visible there too. PRs also get analyzed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants