Skip to content

CMP-3739: Setup CI for compliance-sdk library#69409

Closed
rhmdnd wants to merge 1 commit intoopenshift:masterfrom
rhmdnd:add-compliance-sdk-ci
Closed

CMP-3739: Setup CI for compliance-sdk library#69409
rhmdnd wants to merge 1 commit intoopenshift:masterfrom
rhmdnd:add-compliance-sdk-ci

Conversation

@rhmdnd
Copy link
Contributor

@rhmdnd rhmdnd commented Sep 18, 2025

We have a library that contains a CEL scanner for integrating into the
Compliance Operator, making it easier for users to define their own
compliance checks.

This commit sets up some initial CI jobs that we can start using to gate
the project.

@rhmdnd
Copy link
Contributor Author

rhmdnd commented Sep 18, 2025

cc: @Vincent056

@openshift-ci openshift-ci bot requested review from Prucek and psalajova September 18, 2025 02:36
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 18, 2025
@rhmdnd rhmdnd changed the title Setup CI for compliance-sdk library CMP-3739: Setup CI for compliance-sdk library Sep 18, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 18, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 18, 2025 •
edited by openshift-ci bot
Loading

@rhmdnd: This pull request references CMP-3739 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

We have a library that contains a CEL scanner for integrating into the
Compliance Operator, making it easier for users to define their own
compliance checks.

This commit sets up some initial CI jobs that we can start using to gate
the project.

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 openshift-eng/jira-lifecycle-plugin repository.

rhmdnd added a commit to ComplianceAsCode/compliance-sdk that referenced this pull request Sep 18, 2025
@rhmdnd
CMP-3739: Add OWNERS file
f930759 
Add an initial owners file for reviewers and approvers. This is a
prerequisite for CI in openshift/release#69409.
@rhmdnd rhmdnd mentioned this pull request Sep 18, 2025
Open
@rhmdnd rhmdnd force-pushed the add-compliance-sdk-ci branch 3 times, most recently from a195c4f to 8582307 Compare September 18, 2025 12:08
@rhmdnd rhmdnd force-pushed the add-compliance-sdk-ci branch 2 times, most recently from 96cf01d to 56fc06c Compare September 18, 2025 13:28
@rhmdnd
Setup CI for compliance-sdk library
f484039 
We have a library that contains a CEL scanner for integrating into the
Compliance Operator, making it easier for users to define their own
compliance checks.

This commit sets up some initial CI jobs that we can start using to gate
the project.
@rhmdnd rhmdnd force-pushed the add-compliance-sdk-ci branch from 56fc06c to f484039 Compare September 18, 2025 13:30
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 18, 2025

[REHEARSALNOTIFIER]
@rhmdnd: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-integration-tests ComplianceAsCode/compliance-sdk presubmit Presubmit changed
pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-lint ComplianceAsCode/compliance-sdk presubmit Presubmit changed
pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-unit-tests ComplianceAsCode/compliance-sdk presubmit Presubmit changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

1 similar comment
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 18, 2025

[REHEARSALNOTIFIER]
@rhmdnd: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-integration-tests ComplianceAsCode/compliance-sdk presubmit Presubmit changed
pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-lint ComplianceAsCode/compliance-sdk presubmit Presubmit changed
pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-unit-tests ComplianceAsCode/compliance-sdk presubmit Presubmit changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@rhmdnd
Copy link
Contributor Author

rhmdnd commented Sep 18, 2025

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Sep 18, 2025

@rhmdnd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@rhmdnd
Copy link
Contributor Author

rhmdnd commented Sep 18, 2025

/test all

rhmdnd added a commit to rhmdnd/compliance-sdk that referenced this pull request Sep 18, 2025
@rhmdnd
CMP-3739: Add a noop integration test target
cd99857 
We're setting up the ability to run integration tests that exercise how
the library works against a real OpenShift cluster in
openshift/release#69409.

This commit adds a new make target so that we can run integration tests
in isolation, making it easier to have dedicated jobs for specific test
scenarios.
rhmdnd added a commit to rhmdnd/compliance-sdk that referenced this pull request Sep 18, 2025
@rhmdnd
CMP-3739: Add a noop integration test target
13dc0e4 
We're setting up the ability to run integration tests that exercise how
the library works against a real OpenShift cluster in
openshift/release#69409.

This commit adds a new make target so that we can run integration tests
in isolation, making it easier to have dedicated jobs for specific test
scenarios.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 18, 2025

@rhmdnd: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/ComplianceAsCode/compliance-sdk/main/compliance-sdk-unit-tests f484039 link unknown /pj-rehearse pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-unit-tests
ci/rehearse/ComplianceAsCode/compliance-sdk/main/compliance-sdk-lint f484039 link unknown /pj-rehearse pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-lint
ci/prow/check-gh-automation f484039 link true /test check-gh-automation
ci/rehearse/ComplianceAsCode/compliance-sdk/main/compliance-sdk-integration-tests f484039 link unknown /pj-rehearse pull-ci-ComplianceAsCode-compliance-sdk-main-compliance-sdk-integration-tests

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@rhmdnd
Copy link
Contributor Author

rhmdnd commented Sep 19, 2025

We'll need to land ComplianceAsCode/compliance-sdk#4 before these rehearsals pass.

@rhmdnd rhmdnd mentioned this pull request Sep 19, 2025
Open
@openshift-bot
Copy link
Contributor

openshift-bot commented Oct 19, 2025

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2025
@openshift-bot
Copy link
Contributor

openshift-bot commented Nov 3, 2025

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 3, 2025
@openshift-bot
Copy link
Contributor

openshift-bot commented Nov 18, 2025

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Nov 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Prucek Prucek Awaiting requested review from Prucek

@psalajova psalajova Awaiting requested review from psalajova

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@rhmdnd @openshift-ci-robot @openshift-bot