openshift
WIP: Test checking for oc command rather than looking for file.
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@CrystalChun: The following commands are available to trigger required jobs:
/test e2e-agent-compact-ipv4
/test edge-e2e-ai-operator-ztp
/test edge-e2e-metal-assisted-4-18
/test edge-format-check
/test edge-images
/test edge-lint
/test edge-unit-test
/test images
/test mce-images
The following commands are available to trigger optional jobs:
/test e2e-agent-4control-ipv4
/test e2e-agent-5control-ipv4
/test e2e-agent-ha-dualstack
/test e2e-agent-sno-ipv6
/test edge-e2e-metal-assisted-cnv-4-17
/test edge-e2e-metal-assisted-external-4-18
/test edge-e2e-metal-assisted-ipv6-4-18
/test edge-e2e-metal-assisted-lvm-4-18
/test edge-e2e-metal-assisted-odf-4-17
/test edge-e2e-metal-assisted-single-node-4-18
/test edge-e2e-oci-assisted-4-18
/test edge-e2e-vsphere-assisted-4-18
/test edge-publish-multi-arch-images-dry-run
/test okd-scos-e2e-aws-ovn
/test okd-scos-images
Use /test all to run the following jobs that were automatically triggered:
pull-ci-openshift-assisted-installer-master-e2e-agent-compact-ipv4
pull-ci-openshift-assisted-installer-master-edge-e2e-ai-operator-ztp
pull-ci-openshift-assisted-installer-master-edge-e2e-metal-assisted-4-18
pull-ci-openshift-assisted-installer-master-edge-format-check
pull-ci-openshift-assisted-installer-master-edge-images
pull-ci-openshift-assisted-installer-master-edge-lint
pull-ci-openshift-assisted-installer-master-edge-unit-test
pull-ci-openshift-assisted-installer-master-images
pull-ci-openshift-assisted-installer-master-mce-images
pull-ci-openshift-assisted-installer-master-okd-scos-e2e-aws-ovn
In response to this:
/test ?
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: CrystalChun
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [CrystalChun]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@CrystalChun: all tests passed!
Full PR test history. Your PR dashboard.
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d 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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d 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
Rotten issues close after 30d 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-bot: Closed this PR.
In response to this:
Rotten issues close after 30d 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.