Spinnaker Pipeline Template: Difference between revisions
| Line 10: | Line 10: | ||
==Pipeline Template== | ==Pipeline Template== | ||
===Template=== | ===Template=== | ||
A template defines a parameterized pipeline, with the set of [[#Variable|variables]] for which the users instantiating the template will provide values. The template does not have the [[Spinnaker_Concepts#Pipeline_Configuration|pipeline configuration]] found on a pipeline instance. | A template defines a parameterized pipeline, with the set of [[#Variable|variables]] for which the users instantiating the template will provide values. The template does not have the [[Spinnaker_Concepts#Pipeline_Configuration|pipeline configuration]] found on a pipeline instance. The template is useful in defining a pipeline pattern that can be instantiated as multiple concrete pipeline instances. | ||
===Configuration=== | ===Configuration=== | ||
Revision as of 21:07, 22 May 2023
External
- https://spinnaker.io/docs/concepts/pipelines/#pipeline-templates
- https://spinnaker.io/docs/reference/pipeline/templates/
Internal
Overview
Multiple pipeline instances can be created from a pipeline template. A pipeline template has two components: the template and the configuration.
Concepts
Pipeline Template
Template
A template defines a parameterized pipeline, with the set of variables for which the users instantiating the template will provide values. The template does not have the pipeline configuration found on a pipeline instance. The template is useful in defining a pipeline pattern that can be instantiated as multiple concrete pipeline instances.
Configuration
A pipeline template configuration is a concrete implementation of a template. Configurations can inject new stages into the final pipeline graph and inherit or override, or both, triggers, notifications, and parameters.
Variable
Pipeline
Whether it’s created from a template or not, an executable pipeline that can be visualized in the UI.