-
Notifications
You must be signed in to change notification settings - Fork 2.3k
openshift-pipelines/console-plugin: Replace Cypress e2e with Playwright #83396
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
Open
bharatmajjiga
wants to merge
1
commit into
openshift:main
Choose a base branch
from
bharatmajjiga:playwright-e2e-console-plugin
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+32
−5
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/release
Length of output: 50374
🏁 Script executed:
Repository: openshift/release
Length of output: 50373
🏁 Script executed:
Repository: openshift/release
Length of output: 50374
🌐 Web query:
OpenShift ci-operator test step YAMLcli: latestmeaning and whether it overrides the test image's oc binary; find upstream documentation or source💡 Result:
In OpenShift ci-operator test step YAML, the configuration
cli: latestinstructs the operator to inject the OpenShift CLI (oc binary) from the "latest" release payload into the container environment where the test step is executed [1][2][3]. Specifically: 1. Meaning: Theclifield specifies which OpenShift release payload should be used as the source for the oc binary [1]. Usingcli: latesttells ci-operator to source this binary from the ephemeral release payload associated with the "latest" tag, which typically corresponds to the version of OpenShift being tested or installed in the CI job [4][5][6]. 2. Overriding Behavior: It does not necessarily "override" an existing oc binary already present in the test image in the sense of deleting or replacing files on the base image disk. Instead, it ensures the oc binary from the specified release is made available to the step (often by mounting it into the container or updating the PATH) so that commands run within that step use the version from the requested release [1][2]. If an oc binary was already present in the test image, the injected binary from the release payload will generally take precedence in the execution environment, ensuring that the test commands run with the expected version of the CLI [1][3]. Upstream Documentation Source: This functionality is documented in the OpenShift CI documentation, particularly within the sections covering the Step Registry and Multi-stage tests [1][2]. You can find technical details on how steps inject the CLI in the OpenShift CI documentation under the "Step Registry" and "Migrating CI Jobs" sections [1][2]. References: [1] https://github.com/openshift/ci-docs/blob/main/content/en/architecture/step-registry.md [2] https://docs.ci.openshift.org/how-tos/migrating-template-jobs-to-multistage/Citations:
🏁 Script executed:
Repository: openshift/release
Length of output: 50376
🏁 Script executed:
Repository: openshift/release
Length of output: 1275
Use an immutable
playwright-runnerimage.ui-ci:latestis mutable and can change the Playwright, browser, or Python dependencies without a configuration change. Pin a verified digest.cli: latestalready resolves throughreleases.latestto theocp/4.21payload.🤖 Prompt for AI Agents