search

ComplianceAsCode / content

Security automation content in SCAP, Bash, Ansible, and other formats
https://complianceascode.readthedocs.io/en/latest/
Other
2.22k stars 698 forks source link

Add workflow to trigger OCP tests #12542

Closed yuumasato closed 2 weeks ago

yuumasato commented 4 weeks ago

Description:

Rationale:

Review Hints:

github-actions[bot] commented 4 weeks ago

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment Open in Gitpod

Oracle Linux 8 Environment Open in Gitpod

github-actions[bot] commented 3 weeks ago

:robot: Trigger prow tests based on changed rules

/test 4.17-e2e-aws-ocp4-moderate-rev-4 /test 4.17-e2e-aws-ocp4-pci-dss-node

github-actions[bot] commented 3 weeks ago

:robot: Trigger prow tests based on changed rules

/test 4.17-e2e-aws-ocp4-pci-dss-3-2 /test 4.17-e2e-aws-ocp4-pci-dss-node-3-2

Note: if a test is not started it can be that a CI Job is not configure for that particular profile or product.

Click here to see all the relevant profiles - -
openshift-ci[bot] commented 3 weeks ago

@github-actions[bot]: The specified target(s) for /test were not found. The following commands are available to trigger required jobs:

Use /test all to run the following jobs that were automatically triggered:

In response to [this](https://github.com/ComplianceAsCode/content/pull/12542#issuecomment-2438868226): >:robot: Trigger prow tests based on changed rules > >/test 4.17-e2e-aws-ocp4-pci-dss-3-2 >/test 4.17-e2e-aws-ocp4-pci-dss-node-3-2 > >Note: if a test is not started it can be that a CI Job is not configure for that particular profile or product. > >
>Click here to see all the relevant profiles > >- >- > >

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.

github-actions[bot] commented 3 weeks ago

:robot: Trigger prow tests based on changed rules

/test 4.17-e2e-aws-ocp4-high-node /test 4.16-e2e-aws-ocp4-high-node /test 4.17-e2e-aws-ocp4-moderate /test 4.16-e2e-aws-ocp4-moderate

Note: if a test is not started it could be that a CI Job is not configure for that particular profile or product.

Click here to see all the relevant profiles - `-e2e-aws-ocp4-bsi-node` - `-e2e-aws-ocp4-bsi` - `-e2e-aws-ocp4-cis-node` - `-e2e-aws-ocp4-cis` - `-e2e-aws-ocp4-e8` - `-e2e-aws-ocp4-high-node` - `-e2e-aws-ocp4-high` - `-e2e-aws-ocp4-moderate-node` - `-e2e-aws-ocp4-moderate` - `-e2e-aws-ocp4-pci-dss-4-0` - `-e2e-aws-ocp4-pci-dss-node-4-0` - `-e2e-aws-ocp4-pci-dss-node` - `-e2e-aws-ocp4-pci-dss` - `-e2e-aws-ocp4-stig`
yuumasato commented 3 weeks ago

Handling for profiles that don't have a CI job was added.

This seems to be working fine, Prow is detects the comment and starts tests:

yuumasato commented 3 weeks ago

Workflow logs: https://github.com/ComplianceAsCode/content/actions/runs/11551324559/job/32148092439?pr=12542

yuumasato commented 3 weeks ago

I have dropped the artificial change: b7c47b01ba4c2f2a7b666ca7108cb23aa7bf3ee6. This is ready for review/merge.

github-actions[bot] commented 3 weeks ago

:robot: Trigger prow tests based on changed rules

/test e2e-aws-ocp4-high-node /test e2e-aws-ocp4-moderate

Note: if a test is not started it could be that a CI Job is not configure for that particular profile or product.

Click here to see all the relevant profiles - `-e2e-aws-ocp4-bsi-node` - `-e2e-aws-ocp4-bsi` - `-e2e-aws-ocp4-cis-node` - `-e2e-aws-ocp4-cis` - `-e2e-aws-ocp4-e8` - `-e2e-aws-ocp4-high-node` - `-e2e-aws-ocp4-high` - `-e2e-aws-ocp4-moderate-node` - `-e2e-aws-ocp4-moderate` - `-e2e-aws-ocp4-pci-dss-4-0` - `-e2e-aws-ocp4-pci-dss-node-4-0` - `-e2e-aws-ocp4-pci-dss-node` - `-e2e-aws-ocp4-pci-dss` - `-e2e-aws-ocp4-stig`
openshift-ci[bot] commented 3 weeks ago

@yuumasato: 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/prow/4.17-e2e-aws-ocp4-pci-dss-node f677259ad8da55f343acd07f913dfc20abb8830c link true /test 4.17-e2e-aws-ocp4-pci-dss-node
ci/prow/4.16-e2e-aws-ocp4-high-node b7c47b01ba4c2f2a7b666ca7108cb23aa7bf3ee6 link true /test 4.16-e2e-aws-ocp4-high-node
ci/prow/4.17-e2e-aws-ocp4-high-node b7c47b01ba4c2f2a7b666ca7108cb23aa7bf3ee6 link true /test 4.17-e2e-aws-ocp4-high-node
ci/prow/4.17-e2e-aws-ocp4-moderate b7c47b01ba4c2f2a7b666ca7108cb23aa7bf3ee6 link true /test 4.17-e2e-aws-ocp4-moderate
ci/prow/e2e-aws-ocp4-high-node 7b46c13a9e32631649c0376873f74ddb169ec951 link true /test e2e-aws-ocp4-high-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
yuumasato commented 3 weeks ago

I'm dropping 7b46c13a9e32631649c0376873f74ddb169ec951since the workflow ran successfully.

codeclimate[bot] commented 3 weeks ago

Code Climate has analyzed commit 29994432 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 60.9% (0.0% change).

View more on Code Climate.

rhmdnd commented 2 weeks ago

/packit retest-failed