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

Update github workflows #784

Merged
merged 1 commit into from
Aug 1, 2023
Merged

Update github workflows #784

merged 1 commit into from
Aug 1, 2023

Conversation

sergiught
Copy link
Contributor

@sergiught sergiught commented Jul 31, 2023

🔧 Changes

Updates to the CI pipeline:

  • Move govulncheck to Security workflow
  • Update go setup to v4.
  • Remove deferred trigger PR workflow so the security jobs can trigger

📚 References

🔬 Testing

📝 Checklist

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

@sergiught sergiught force-pushed the patch/update-ci branch 2 times, most recently from c87465f to 7ae0ecb Compare July 31, 2023 16:02
@sergiught sergiught marked this pull request as ready for review August 1, 2023 09:08
@sergiught sergiught requested a review from a team as a code owner August 1, 2023 09:08
push:
branches: [ "main" ]
schedule:
- cron: "30 0 1,15 * *"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be running on a cron?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, as otherwise it would only trigger when there is activity on this repo. But in case there isn't any, we still want to trigger this security check so we can get alerted if any dependencies have had vulnerabilities discovered.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't that be done by Dependabot and Snyk anyway?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's done also by Dependabot and Snyk, correct. From my understanding we need both snyk, semgrep and govulncheck to maximize the chance of being alerted on issues, so we don't have just a single point of failure for security checks.

I'll cc: @evansims and @poovamraj tho to confirm.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 Yup! Snyk is excellent, but its handling of Go has not proven to be the most reliable in our past experiences. On the other hand, Govulncheck has proven quite reliable. Having it as an additional security filter here makes sense. 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @evansims!

@sergiught sergiught requested a review from evansims August 1, 2023 10:28
@sergiught sergiught merged commit ae12386 into main Aug 1, 2023
7 checks passed
@sergiught sergiught deleted the patch/update-ci branch August 1, 2023 13:35
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.

3 participants