Bug 1838792 - [openshift-4.4] Handle embedded pipelineSpec in pipelineRun details page.
Summary: [openshift-4.4] Handle embedded pipelineSpec in pipelineRun details page.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: All
OS: All
high
urgent
Target Milestone: ---
: 4.4.z
Assignee: Karthik Jeeyar
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On: 1835228
Blocks: 1839036
TreeView+ depends on / blocked
 
Reported: 2020-05-21 19:27 UTC by Karthik Jeeyar
Modified: 2020-06-02 11:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Embedded pipeline spec is not supported in UI Consequence: When the user creates the pipelinerun via cli or using the yaml https://gist.githubusercontent.com/praveen4g0/417eb5c173831a18b85737e45f564e12/raw/9e8a717936a213c86abcbb8a9af16c13d29838e3/embeededpipelinespec.yaml, it breaks the UI Fix: Add additional checks to fix avoid the error in the UI Result: UI will not break in the embedded pipeline scenario
Clone Of: 1835228
: 1839036 (view as bug list)
Environment:
Last Closed: 2020-06-02 11:18:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Handle embedded pipelineSpec in pipelineRun details page (50.55 KB, image/png)
2020-05-26 10:51 UTC, spathak@redhat.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5526 0 None closed Bug 1838792: handle embedded pipeline spec in pipelinerun scenario 2020-07-01 01:39:04 UTC
Red Hat Product Errata RHBA-2020:2310 0 None None None 2020-06-02 11:18:56 UTC

Comment 3 spathak@redhat.com 2020-05-26 10:51:50 UTC 
Created attachment 1692229 [details]
Handle embedded pipelineSpec in pipelineRun details page
Comment 4 spathak@redhat.com 2020-05-26 10:52:22 UTC 
Validated on build version:4.4.0-0.ci-2020-05-25-181336
Browser version: Chrome 81
Comment 6 errata-xmlrpc 2020-06-02 11:18:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2310
Note You need to log in before you can comment on or make changes to this bug.