Bug 1796185
Summary: | Enable pipelines for Knative and Kubernetes apps on import | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Andrew Ballantyne <aballant> | ||||||
Component: | Dev Console | Assignee: | Andrew Ballantyne <aballant> | ||||||
Status: | CLOSED ERRATA | QA Contact: | spathak <spathak> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 4.4 | CC: | aos-bugs, nmukherj, spathak | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 4.5.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: |
Cause:
Pipeline templates provided by the Operator had a Deployment Config specific deploy step, and would fail for Deployment and Knative Services
Consequence:
The Pipeline would build your app but not deploy it.
Fix:
Added support for the add flow to make use of the resource type as well as the builder to determine a Pipeline
Result:
Resource-specific support for Pipeline templates
|
Story Points: | --- | ||||||
Clone Of: | |||||||||
: | 1796186 1807133 (view as bug list) | Environment: | |||||||
Last Closed: | 2020-07-13 17:13:32 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1807133 | ||||||||
Attachments: |
|
Description
Andrew Ballantyne
2020-01-29 19:33:22 UTC
Created attachment 1667322 [details]
Enable pipelines for Knative and Kubernetes apps on import
Verified on build : 4.5.0-0.ci-2020-03-03-154145 Chrome browser: 76.0.3809.132 Created attachment 1667506 [details]
Enable pipelines for Knative and Kubernetes apps on import screenshot
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:2409 |