[release-4.12] OCPBUGS-6085: Editing Pipeline in the ocp console should show correct information

[openshift-cherrypick-robot]

This is an automated cherry-pick of #12446

/assign debsmita1

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-5016 has been cloned as Jira Issue OCPBUGS-6085. Retitling PR to link against new bug.
/retitle [release-4.12] OCPBUGS-6085: Editing Pipeline in the ocp console should show correct information

In response to this:

This is an automated cherry-pick of #12446

/assign debsmita1

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/test-infra repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-6085, which is invalid:

• expected dependent Jira Issue OCPBUGS-5016 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #12446

/assign debsmita1

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/test-infra repository.

[openshift-ci]

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.12] OCPBUGS-6085: Editing Pipeline in the ocp console should show correct information

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/test-infra repository.

[debsmita1]

/assign @vikram-raj

[vikram-raj]

Verified it on 4.12 cluster bot

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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/pipelines-plugin/OWNERS [vikram-raj]

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

[vikram-raj]

/jira refresh

[openshift-ci-robot]

@vikram-raj: This pull request references Jira Issue OCPBUGS-6085, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.12.z) matches configured target version for branch (4.12.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-5016 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-5016 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
• bug has dependents

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

/jira refresh

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/test-infra repository.

[vikram-raj]

/retest

[jerolimov]

/label backport-risk-assessed

[hemantsaini-7]

/label cherry-pick-approved

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD e9c7ec8 and 2 for PR HEAD 59d7337 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 8b7f0f2 and 1 for PR HEAD 59d7337 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 033f5a0 and 0 for PR HEAD 59d7337 in total

[openshift-ci]

@openshift-cherrypick-robot: 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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

• openshift/console#12452

Jira Issue OCPBUGS-6085 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #12446

/assign debsmita1

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/test-infra repository.

[vikram-raj]

/cherry-pick release-4.11

[openshift-cherrypick-robot]

@vikram-raj: #12452 failed to apply on top of branch "release-4.11":

Applying: Editing Pipeline in the ocp console should show correct information
Using index info to reconstruct a base tree...
M	frontend/packages/pipelines-plugin/src/components/pipelines/pipeline-builder/utils.ts
Falling back to patching base and 3-way merge...
Auto-merging frontend/packages/pipelines-plugin/src/components/pipelines/pipeline-builder/utils.ts
CONFLICT (content): Merge conflict in frontend/packages/pipelines-plugin/src/components/pipelines/pipeline-builder/utils.ts
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Editing Pipeline in the ocp console should show correct information
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.11

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/test-infra repository.

[jerolimov]

Backport for 4.11 is #12540