-
Notifications
You must be signed in to change notification settings - Fork 139
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
fix: The clair-scan task is not required for FBC pipelines #1065
Conversation
In release-engineering/rhtap-ec-policy#19, I removed the requirement of multiple checks for FBC pipelines due to their special nature where the images produced are not themsleves pushed, instead metadata is extracted from it and published to the index for OLM. Therefore, we no longer need to require clair-scan images to be present for these pipelines either. Signed-off-by: arewm <[email protected]>
Quality Gate passedIssues Measures |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tisutisu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is follow-on work from the following PRs: release-engineering/rhtap-ec-policy#19 konflux-ci/e2e-tests#1065 Signed-off-by: arewm <[email protected]>
This is follow-on work from the following PRs: - release-engineering/rhtap-ec-policy#19 - konflux-ci/e2e-tests#1065 Signed-off-by: arewm <[email protected]>
This is follow-on work from the following PRs: - release-engineering/rhtap-ec-policy#19 - konflux-ci/e2e-tests#1065 Signed-off-by: arewm <[email protected]>
In release-engineering/rhtap-ec-policy#19, I removed the requirement of multiple checks for FBC pipelines due to their special nature where the images produced are not themsleves pushed, instead metadata is extracted from it and published to the index for OLM.
Therefore, we no longer need to require clair-scan images to be present for these pipelines either.
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue ticket number and link
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: