Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Undefined
Fix Version/s: Pipelines 1.10.0
Affects Version/s: Pipelines 1.8.0
Component/s: Operator, Pipelines as Code
Labels:
None

Story Points:
1
Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:

Hide
Currently Openshift Console UI have hardcoded PipelineRun template as a fallback template if a template for runtime (go, java, python, nodejs) is not found in the Openshift namespace.

The ask from console team is It would be nice if a default PipelineRun template(Generic) should be provided in a ConfigMap pipelines-as-code-template-default by the OSP operator so that console can rely on that instead of hardcoded PipelineRun template.

Show
Currently Openshift Console UI have hardcoded PipelineRun template as a fallback template if a template for runtime (go, java, python, nodejs) is not found in the Openshift namespace. The ask from console team is It would be nice if a default PipelineRun template(Generic) should be provided in a ConfigMap pipelines-as-code-template-default by the OSP operator so that console can rely on that instead of hardcoded PipelineRun template.
Git Pull Request:
https://github.com/tektoncd/operator/pull/1356, https://github.com/tektoncd/operator/pull/1357
Intelligence Requested:
Market:

Sprint:
Pipelines Sprint 232, Pipelines Sprint 233, Pipelines Sprint 234, Pipelines Sprint 235

SFDC Cases Counter:
SFDC Cases Links:

Description of problem:

In Openshift Console UI we have a hardcoded PipelineRun template as a fallback template if a template for runtime is not found in the Openshift namespace. It would be nice if a default PipelineRun template should be provided in a ConfigMap name `pipelines-as-code-template-default` by the OSP operator.

Template hardcoded in the UI https://github.com/openshift/console/blob/master/frontend/packages/pipelines-plugin/src/components/repository/repository-form-utils.ts#L186