Skip to content

[release-4.23] OU-1240: Makefile and package.json to enable test-frontend-ci#1098

Closed
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-4.23from
openshift-cherrypick-robot:cherry-pick-1091-to-release-4.23
Closed

[release-4.23] OU-1240: Makefile and package.json to enable test-frontend-ci#1098
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-4.23from
openshift-cherrypick-robot:cherry-pick-1091-to-release-4.23

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1091

/assign etmurasaki

@openshift-ci-robot

openshift-ci-robot commented Jul 27, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OU-1240

Details

In response to this:

This is an automated cherry-pick of #1091

/assign etmurasaki

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 PeterYurkovich and zhuje July 27, 2026 02:35
@etmurasaki

Copy link
Copy Markdown
Contributor

/lgtm

@etmurasaki

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Jul 27, 2026
@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 27, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 27, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references OU-1240 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.23.0" version, but no target version was set.

Details

In response to this:

This is an automated cherry-pick of #1091

/assign etmurasaki

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 Jul 27, 2026
@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: etmurasaki, openshift-cherrypick-robot

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 Jul 27, 2026
@etmurasaki

Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-monitoring

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@etmurasaki: Overrode contexts on behalf of etmurasaki: ci/prow/e2e-monitoring

Details

In response to this:

/override ci/prow/e2e-monitoring

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.

@etmurasaki

Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-management-api

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@etmurasaki: Overrode contexts on behalf of etmurasaki: ci/prow/e2e-management-api

Details

In response to this:

/override ci/prow/e2e-management-api

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-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 0d9faac and 2 for PR HEAD afc516f in total

@jgbernalp

Copy link
Copy Markdown
Contributor

/override ci/prow/e2e-management-api

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@jgbernalp: Overrode contexts on behalf of jgbernalp: ci/prow/e2e-management-api

Details

In response to this:

/override ci/prow/e2e-management-api

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

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-management-api afc516f link true /test e2e-management-api

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.

@jgbernalp

Copy link
Copy Markdown
Contributor

@etmurasaki 4.23 and 5.0 are still tracking main. So we should not merge PRs directly to those branches. I'll close this PR.

@jgbernalp jgbernalp closed this Jul 27, 2026
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants