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

Automated backport of #1517: Only fail builds for high+ vulns #1524

Conversation

skitt
Copy link
Member

@skitt skitt commented Mar 26, 2024

Backport of #1517 on release-0.15.

#1517: Only fail builds for high+ vulns

For details on the backport process, see the backport requests page.

Since the vulnerability scan doesn't distinguish between
vulnerabilities added by the PR and those coming from vulnerability
updates, PRs are regularly blocked because of unrelated
vulnerabilities. Arguably this is desirable for important
vulnerabilities since it forces them to be handled; but other
vulnerabilities shouldn't block PRs.

This changes the fail threshold to high, so that only vulnerabilities
with severity high or critical will block the build.

Signed-off-by: Stephen Kitt <[email protected]>
@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr1524/skitt/automated-backport-of-#1517-origin-release-0.15
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Mar 26, 2024
@tpantelis tpantelis enabled auto-merge (rebase) March 26, 2024 14:14
@tpantelis tpantelis merged commit 2f8a7c0 into submariner-io:release-0.15 Mar 26, 2024
29 of 30 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr1524/skitt/automated-backport-of-#1517-origin-release-0.15]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated-backport ready-to-test When a PR is ready for full E2E testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants