ODC-7782: Test adjustments to perspective merge

[sanketpathak]

Story:ODC-7782

Description:
Test adjustments to perspective merge

Command to execute:

export NO_HEADLESS=true && export CHROME_VERSION=$(/usr/bin/google-chrome-stable --version)
BRIDGE_KUBEADMIN_PASSWORD=YH3jN-PRFT2-Q429c-5KQDr
BRIDGE_BASE_ADDRESS=https://console-openshift-console.apps.dev-svc-4.13-042801.devcluster.openshift.com/
export BRIDGE_KUBEADMIN_PASSWORD
export BRIDGE_BASE_ADDRESS
oc login -u kubeadmin -p $BRIDGE_KUBEADMIN_PASSWORD
oc apply -f ./frontend/packages/console-shared/src/test-data/htpasswd-secret.yaml
oc patch oauths cluster --patch "$(cat ./frontend/packages/console-shared/src/test-data/patch-htpasswd.yaml)" --type=merge
In frontend folder run
./integration-tests/test-cypress.sh -p knative
Run eventing-page-admin, filters-serving-eventing-admin, serverless-admin-empty-state, serving-page-admin files
Browser
Chrome 125

[openshift-ci-robot]

@sanketpathak: This pull request references ODC-7782 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.19.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-robot]

@sanketpathak: This pull request references ODC-7782 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.19.0" version, but no target version was set.

In response to this:

Story:ODC-7782

Description:
Test adjustments to perspective merge

Command to execute:

export NO_HEADLESS=true && export CHROME_VERSION=$(/usr/bin/google-chrome-stable --version)
BRIDGE_KUBEADMIN_PASSWORD=YH3jN-PRFT2-Q429c-5KQDr
BRIDGE_BASE_ADDRESS=https://console-openshift-console.apps.dev-svc-4.13-042801.devcluster.openshift.com/
export BRIDGE_KUBEADMIN_PASSWORD
export BRIDGE_BASE_ADDRESS
oc login -u kubeadmin -p $BRIDGE_KUBEADMIN_PASSWORD
oc apply -f ./frontend/packages/console-shared/src/test-data/htpasswd-secret.yaml
oc patch oauths cluster --patch "$(cat ./frontend/packages/console-shared/src/test-data/patch-htpasswd.yaml)" --type=merge
In frontend folder run
./integration-tests/test-cypress.sh -p knative
Run eventing-page-admin, filters-serving-eventing-admin, serverless-admin-empty-state, serving-page-admin files
Browser
Chrome 125

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sanketpathak

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:

• frontend/packages/console-telemetry-plugin/integration-tests/OWNERS [sanketpathak]
• frontend/packages/dev-console/integration-tests/OWNERS [sanketpathak]
• frontend/packages/helm-plugin/integration-tests/OWNERS [sanketpathak]
• frontend/packages/knative-plugin/integration-tests/OWNERS [sanketpathak]
• frontend/packages/pipelines-plugin/integration-tests/OWNERS [sanketpathak]
• frontend/packages/shipwright-plugin/integration-tests/OWNERS [sanketpathak]
• frontend/packages/topology/integration-tests/OWNERS [sanketpathak]
• frontend/packages/webterminal-plugin/integration-tests/OWNERS [sanketpathak]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sanketpathak]

/retest

[openshift-ci]

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