Skip to content

CFE-1049: Add tech-preview e2e in CI config for cluster-network-operator#51201

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
arkadeepsen:techpreview-e2e
Apr 23, 2024
Merged

CFE-1049: Add tech-preview e2e in CI config for cluster-network-operator#51201
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
arkadeepsen:techpreview-e2e

Conversation

@arkadeepsen
Copy link
Copy Markdown
Member

This PR add CI configuration for running tech-preview e2e test in GCP for cluster-network-operator. This will test the new e2e test added in openshift/origin#28683.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 22, 2024

@arkadeepsen: This pull request references CFE-1049 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.16.0" version, but no target version was set.

Details

In response to this:

This PR add CI configuration for running tech-preview e2e test in GCP for cluster-network-operator. This will test the new e2e test added in openshift/origin#28683.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 22, 2024
@arkadeepsen
Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-openshift-cluster-network-operator-master-e2e-gcp-ovn-techpreview

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

secretName: result-aggregator
trigger: (?m)^/test( | .* )e2e-gcp-ovn,?($|\s.*)
- agent: kubernetes
always_run: true
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you want this running every time? or is it just a job we want to be able to trigger from time to time with the /test commend in github?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can surely make it optional. I'll make the changes.

@jluhrsen
Copy link
Copy Markdown
Contributor

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@arkadeepsen: 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-openshift-cluster-network-operator-master-e2e-gcp-ovn-techpreview openshift/cluster-network-operator 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 abort to abort all active rehearsals

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.

@arkadeepsen
Copy link
Copy Markdown
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@jluhrsen
Copy link
Copy Markdown
Contributor

/lgtm

@jluhrsen
Copy link
Copy Markdown
Contributor

/pj-rehearse ack

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2024
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 22, 2024
@jcaamano
Copy link
Copy Markdown
Contributor

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arkadeepsen, jcaamano, jluhrsen

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 Apr 23, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 23, 2024

@arkadeepsen: all tests passed!

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

@openshift-merge-bot openshift-merge-bot bot merged commit 0343e69 into openshift:master Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants