-
Notifications
You must be signed in to change notification settings - Fork 750
Red Hat Konflux kflux-prd-rh02 update compliance-operator-content-dev #13686
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
base: master
Are you sure you want to change the base?
Red Hat Konflux kflux-prd-rh02 update compliance-operator-content-dev #13686
Conversation
Signed-off-by: red-hat-konflux-kflux-prd-rh02 <[email protected]>
Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR. I'm waiting for a ComplianceAsCode 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-sigs/prow repository. |
800e9e2
to
aa74cb0
Compare
/retest |
Code Climate has analyzed commit df6ad88 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 61.7% (0.0% change). View more on Code Climate. |
/retest |
223463e
to
3fd3cb2
Compare
775be1e
to
9d2803b
Compare
- Add build for Power and Z - Build source iamge - Remove obsolete pipeline
This is a requirement on the images shipped via Konflux
9d2803b
to
edcee07
Compare
Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content
/ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization
Please follow the block sequence indentation style introduced by the proprosed PipelineRuns YAMLs, or keep using consistent indentation level through your customized PipelineRuns. When different levels are mixed, it will be changed to the proposed style.