-
Notifications
You must be signed in to change notification settings - Fork 528
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
CI: Add GitHub Actions workflow for periodic Coverity Scan #1958
Conversation
The build workflow has been tested , as well as the case where secrets are not defined Unfortunately it's not possible to test the scheduled variant's trigger before landing it because of restrictions of github actions: they only run in the main branch for a repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for advancing this PR.
.github/workflows/scheduled.yaml
Outdated
|
||
on: | ||
schedule: | ||
- cron: "42 3 * * 0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope this belated realization convinces you to accept my suggestion, but I still do not have the energy to fight for this specific improvement.
Co-authored-by: Alex Rousskov <[email protected]>
Co-authored-by: Alex Rousskov <[email protected]>
Co-authored-by: Alex Rousskov <[email protected]>
Co-authored-by: Alex Rousskov <[email protected]>
Yes. That instruction is for a different product. Coverity also offers a
GitHub action, but as I learnt from their support, it’s for their
enterprise product and won’t work for the free version we use
|
My primary concerns have been addressed
works for me. Clearing for merge |
Implement a weekly scheduled GitHub Actions workflow to run Coverity Scan (i.e. cov-build). Currently, we run Coverity Scan using Jenkins. The new job uses the Squid Project pre-made docker image because installing the tools required to use free Coverity Scan service cannot be easily automated at the moment. The job only runs for the official Squid Project repository.
Implement a weekly scheduled GitHub Actions workflow to run Coverity
Scan (i.e. cov-build). Currently, we run Coverity Scan using Jenkins.
The new job uses the Squid Project pre-made docker image because
installing the tools required to use free Coverity Scan service cannot
be easily automated at the moment.
The job only runs for the official Squid Project repository.