Skip to content

Conversation

@IshwarKanse
Copy link
Member

@IshwarKanse IshwarKanse commented Jul 18, 2025

  • Implement seamless test reruns and handle test interruptions.
  • Use RBAC TempoStack and TempoMonolithic tests.
  • Use multiarch images so that we can run the tests on IBM P,Z and ARM cluster architectures.
  • Simplifies login.
  • Adds Patternfly element selector commands.
  • Improved documentation.
  • Supports HyperShift logins.
  • Uses Patternfly version agnostic commands and test steps.
  • Uses Cypress best practices.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@IshwarKanse: This pull request references TRACING-5505 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

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.

@IshwarKanse
Copy link
Member Author

/lgtm
/label qe-approved
/label ux-approved

@openshift-ci
Copy link

openshift-ci bot commented Jul 18, 2025

@IshwarKanse: you cannot LGTM your own PR.

In response to this:

/lgtm
/label qe-approved
/label ux-approved

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.

@IshwarKanse
Copy link
Member Author

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

@openshift-ci openshift-ci bot added qe-approved Signifies that QE has signed off on this PR ux-approved Signifies that UX has signed off on this PR labels Jul 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@IshwarKanse: This pull request references TRACING-5505 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

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 openshift-ci bot requested review from jgbernalp and kyoto July 18, 2025 09:16
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 18, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 18, 2025

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e, ci/prow/upstream-amd64-aws-fips-image-scan, ci/prow/upstream-amd64-aws-images, ci/prow/upstream-amd64-aws-lint

In response to this:

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

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.

@IshwarKanse
Copy link
Member Author

/cherry-pick release-1.0

@openshift-cherrypick-robot

@IshwarKanse: once the present PR merges, I will cherry-pick it on top of release-1.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.0

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@IshwarKanse: This pull request references TRACING-5505 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

  • Implement seamless test reruns and handle test interruptions.
  • Use RBAC TempoStack and TempoMonolithic tests.
  • Use multiarch images so that we can run the tests on IBM P,Z and ARM cluster architectures.
  • Simplifies login.
  • Adds Patternfly element selector commands.
  • Improved documentation.
  • Supports HyperShift logins.
  • Uses Patternfly agnostic commands and test steps.
  • Uses Cypress best practices.

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
Copy link

openshift-ci-robot commented Jul 18, 2025

@IshwarKanse: This pull request references TRACING-5505 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 task to target the "4.20.0" version, but no target version was set.

In response to this:

  • Implement seamless test reruns and handle test interruptions.
  • Use RBAC TempoStack and TempoMonolithic tests.
  • Use multiarch images so that we can run the tests on IBM P,Z and ARM cluster architectures.
  • Simplifies login.
  • Adds Patternfly element selector commands.
  • Improved documentation.
  • Supports HyperShift logins.
  • Uses Patternfly version agnostic commands and test steps.
  • Uses Cypress best practices.

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.

@JoaoFula
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 18, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IshwarKanse, JoaoFula

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@IshwarKanse
Copy link
Member Author

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

@openshift-ci
Copy link

openshift-ci bot commented Jul 18, 2025

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e, ci/prow/upstream-amd64-aws-fips-image-scan, ci/prow/upstream-amd64-aws-images, ci/prow/upstream-amd64-aws-lint

In response to this:

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

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.

@IshwarKanse
Copy link
Member Author

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

@openshift-ci
Copy link

openshift-ci bot commented Jul 18, 2025

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e, ci/prow/upstream-amd64-aws-fips-image-scan, ci/prow/upstream-amd64-aws-images, ci/prow/upstream-amd64-aws-lint

In response to this:

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

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.

@openshift-ci
Copy link

openshift-ci bot commented Jul 18, 2025

@IshwarKanse: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit ddaa48b into openshift:main Jul 18, 2025
5 checks passed
@openshift-cherrypick-robot

@IshwarKanse: new pull request created: #137

In response to this:

/cherry-pick release-1.0

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

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. qe-approved Signifies that QE has signed off on this PR ux-approved Signifies that UX has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants