-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Rename CNV conformance and informing jobs to the naming conventions #62005
Rename CNV conformance and informing jobs to the naming conventions #62005
Conversation
According to the CI jobs naming conventions: https://docs.ci.openshift.org/docs/how-tos/naming-your-ci-jobs/, rename the following jobs: e2e-azure-deploy-cnv --> deploy-azure-kubevirt-ovn e2e-kubevirt-azure-ovn-conformance --> e2e-azure-kubevirt-ovn e2e-aws-ovn-virt-techpreview-periodic --> e2e-aws-kubevirt-ovn-techpreview With this naming, it is clear whether the job is running conformance suite (e2e prefix), and that are all related to the kubevirt project. Signed-off-by: Oren Cohen <[email protected]>
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.19-periodics-e2e-aws-kubevirt-ovn-techpreview periodic-ci-openshift-release-master-cnv-nightly-4.19-deploy-azure-kubevirt-ovn periodic-ci-openshift-release-master-cnv-nightly-4.18-deploy-azure-kubevirt-ovn periodic-ci-openshift-release-master-cnv-nightly-4.17-deploy-azure-kubevirt-ovn periodic-ci-openshift-release-master-cnv-nightly-4.16-deploy-azure-kubevirt-ovn periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-azure-kubevirt-ovn |
@orenc1: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Thank you for taking care of this /lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jupierce, orenc1, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/pj-rehearse ack |
@orenc1: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@orenc1: The following test failed, say
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. |
62dd9e2
into
openshift:master
According to the CI jobs naming conventions: https://docs.ci.openshift.org/docs/how-tos/naming-your-ci-jobs/, rename the following jobs:
e2e-azure-deploy-cnv
-->deploy-azure-kubevirt-ovn
e2e-kubevirt-azure-ovn-conformance
-->e2e-azure-kubevirt-ovn
e2e-aws-ovn-virt-techpreview-periodic
-->e2e-aws-kubevirt-ovn-techpreview
With this naming, it is clear whether the job is running conformance suite (e2e prefix), and that are all related to the kubevirt project.