-
Notifications
You must be signed in to change notification settings - Fork 28
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
chore(deps): update rhtap references #95
Conversation
Hi @red-hat-konflux[bot]. Thanks for your PR. I'm waiting for a redhat-appstudio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
7c77a03
to
a1646ea
Compare
/test image-controller-on-pull-request |
@tkdchen: The specified target(s) for
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
8aa1b62
to
d525a45
Compare
d9612d7
to
3e9767d
Compare
29862f5
to
a7e0a83
Compare
a7e0a83
to
f69d598
Compare
The original EC check failed because Tekton Chains took too long to generate the signature and attestation, and the integration service has a known bug where it doesn't always wait for them properly After re-running the EC tests according to https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/testing_applications/proc_retriggering_integration_tests/, there are new violations: violations:
- metadata:
code: cve.cve_results_found
collections:
- minimal
- redhat
depends_on:
- attestation_type.known_attestation_type
description: Confirm that clair-scan task results are present in the SLSA Provenance
attestation of the build pipeline. To exclude this rule add "cve.cve_results_found"
to the `exclude` section of the policy configuration.
solution: Make sure there is a successful task in the build pipeline that runs
a Clair scan and creates a task result called `CLAIR_SCAN_RESULT`.
title: CVE scan results found
msg: Clair CVE scan results were not found The clair scan task did indeed fail in the build pipeline. Retrying |
/retest |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
af08481
to
f69d598
Compare
kubernetes-sigs/controller-runtime#2720 The minimum required Go version for setup-envtes was bumped to 1.22, breaking us. Pin to release-0.16, which doesn't use 1.22 yet. It uses 1.21, which is still higher than what we use, but back then Go didn't enforce the version requirement yet. Signed-off-by: Adam Cmiel <acmiel@redhat.com>
|
@mmorhun: The specified target(s) for
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test images |
This PR contains the following updates:
00402c6
->e1e6c63
9d0f4fa
->5097b69
144c1ab
->628847d
724c2c0
->ba55ff5
e13f6e9
->fffe623
9aa6f81
->c9e991c
a0d054a
->e29adab
e06d355
->422177f
be8d2e7
->e5202b2
3ad20ad
->dce619d
0.1
->0.2
To execute skipped test pipelines write comment
/ok-to-test