Skip to content

NOJIRA: Revert Cypress Cloud enablement for release-4.22#16369

Open
rhamilto wants to merge 1 commit intoopenshift:release-4.22from
rhamilto:revert-16277-release-4.22
Open

NOJIRA: Revert Cypress Cloud enablement for release-4.22#16369
rhamilto wants to merge 1 commit intoopenshift:release-4.22from
rhamilto:revert-16277-release-4.22

Conversation

@rhamilto
Copy link
Copy Markdown
Member

@rhamilto rhamilto commented Apr 28, 2026

Description

This reverts the Cypress Cloud enablement from the release-4.22 branch.

Changes

  • Removes --cloud flag from Cypress test runs
  • Reverts package.json changes that added Cypress Cloud configuration

Testing

CI should run normally without Cypress Cloud integration.

Related PRs

@rhamilto rhamilto changed the title Revert Cypress Cloud enablement for release-4.22 NOJIRA: Revert Cypress Cloud enablement for release-4.22 Apr 28, 2026
@openshift-ci openshift-ci Bot requested review from sanketpathak and spadgett April 28, 2026 18:17
@openshift-ci openshift-ci Bot added component/dev-console Related to dev-console component/helm Related to helm-plugin component/knative Related to knative-plugin approved Indicates a PR has been approved by an approver from all required OWNERS files. component/olm Related to OLM component/topology Related to topology kind/cypress Related to Cypress e2e integration testing labels Apr 28, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 28, 2026

@rhamilto: 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-sigs/prow repository. I understand the commands that are listed here.

@rhamilto
Copy link
Copy Markdown
Member Author

rhamilto commented Apr 29, 2026

/jira refresh
/label backport-risk-assessed

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 29, 2026

@rhamilto: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh
/label backport-risk-assessed

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 added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 29, 2026
logonoff
logonoff approved these changes Apr 29, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

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

/lgtm

@logonoff
Copy link
Copy Markdown
Member

logonoff commented Apr 29, 2026

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 29, 2026

@logonoff: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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 added the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 29, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, rhamilto

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sanketpathak sanketpathak Awaiting requested review from sanketpathak

@spadgett spadgett Awaiting requested review from spadgett

1 more reviewer

@logonoff logonoff logonoff approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@sanketpathak sanketpathak

@logonoff logonoff

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. component/dev-console Related to dev-console component/helm Related to helm-plugin component/knative Related to knative-plugin component/olm Related to OLM component/topology Related to topology kind/cypress Related to Cypress e2e integration testing lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@rhamilto @openshift-ci-robot @logonoff @sanketpathak