-
Notifications
You must be signed in to change notification settings - Fork 58
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
feat(RELEASE-1322): embargo-check internal task uses git resolver #782
base: development
Are you sure you want to change the base?
Conversation
9e2e231
to
9c93c05
Compare
/retest |
/retest |
/retest |
9c93c05
to
855a634
Compare
internal/pipelines/check-embargoed-cves/check-embargoed-cves.yaml
Outdated
Show resolved
Hide resolved
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.
Two small details, but otherwise it looks good.
855a634
to
2839d1e
Compare
This commit updates the embargo-check internal pipeline to call its one task via git resolver. The pipeline itself still uses a cluster resolver, which will be changed in a separate commit. Signed-off-by: Johnny Bieren <[email protected]>
2839d1e
to
32ac587
Compare
@johnbieren: The following test has Failed, say /retest to rerun failed tests.
Inspecting Test ArtifactsTo inspect your test artifacts, follow these steps:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/release-service-catalog:konflux-e2e-tests-catalog-4msmf Test results analysis🚨 Error occurred while running the E2E tests, list of failed Spec(s): ➡️ [ Click to view logsError when waiting for a release pipelinerun for release push-pyxis-rfsy-tenant/snapshot-sample-ylau-6qdln to finish Expected success, but got an error: <*errors.errorString | 0xc0014947c0>: Pipelinerun 'managed-j6xzh' didn't succeed { s: "Pipelinerun 'managed-j6xzh' didn't succeed\n", } ➡️ [ Click to view logsPipelineRun managed-zbvgf failed Expected : Pipelinerun 'managed-zbvgf' didn't succeed\n to equal : ➡️ [ Click to view logsPipelineRun managed-fpnh2 failed Expected : Pipelinerun 'managed-fpnh2' didn't succeed\n to equal : ➡️ [ Click to view logsPipelineRun managed-wxpkc failed Expected : Pipelinerun 'managed-wxpkc' didn't succeed\n to equal : ➡️ [ Click to view logsPipelineRun managed-vw8k7 failed Expected : Pipelinerun 'managed-vw8k7' didn't succeed\n to equal : ➡️ [ Click to view logsPipelineRun managed-2h56v failed Expected : Pipelinerun 'managed-2h56v' didn't succeed\n to equal : ➡️ [ Click to view logsError when waiting for a release pipelinerun for release ex-registry-tuzy-tenant/snapshot-sample-fysb-v2rm8 to finish Expected success, but got an error: <*errors.errorString | 0xc0018efb30>: Pipelinerun 'managed-rxmvc' didn't succeed { s: "Pipelinerun 'managed-rxmvc' didn't succeed\n", } |
/retest |
This commit updates the embargo-check internal pipeline to call its one task via git resolver. The pipeline itself still uses a cluster resolver, which will be changed in a separate commit.
Describe your changes
Relevant Jira
Checklist before requesting a review
do not merge
label if there's a dependency PRrelease-service-maintainers
handle if you are unsure who to tagSigned-off-by: My name <email>