Spinnaker Create a Deployment Pipeline from UI: Difference between revisions
Line 29: | Line 29: | ||
For configuration, see: {{Internal|Spinnaker_Concepts#Docker_Registry|Docker Registry Trigger}} | For configuration, see: {{Internal|Spinnaker_Concepts#Docker_Registry|Docker Registry Trigger}} | ||
====Helm Chart Trigger==== | ====Helm Chart Trigger==== | ||
For configuration, see: {{Internal| | For configuration, see: {{Internal|Spinnaker_Concepts#Helm_Chart_Trigger|Helm Chart Trigger}} | ||
====Artifact Constraints==== | ====Artifact Constraints==== |
Revision as of 00:21, 1 March 2022
External
- https://spinnaker.io/docs/guides/user/pipeline/managing-pipelines/#create-a-pipeline
- https://spinnaker.io/docs/guides/tutorials/codelabs/kubernetes-v2-source-to-prod/
Internal
Overview
This article describes the mechanics of creating a deployment pipeline aimed at performing deployments into a Kubernetes cluster. Also see:
Procedure
Go to the Application to create the pipeline for, select "PIPELINES" from the left menu, and then click on the "Create" button at the top of the page.
Type: Pipeline
Pipeline Name:
Copy From:
Pipeline Configuration
The pipeline configuration allows setting the following elements:
Execution Options
- Disable concurrent pipeline executions (only run one at a time). Set by default.
- Do not automatically cancel pipelines waiting in queue
Automated Triggers
All triggers require specifying permissions, which are the OD groups under whose identity the pipeline will operate when triggered.
Docker Registry Trigger
For configuration, see:
Helm Chart Trigger
For configuration, see:
Artifact Constraints
The section specifies artifacts required for trigger to execute. Only one of the artifacts needs to be present for the trigger to execute. ⚠️ Note that only the artifacts specified here will execute the trigger, it is fine to leave empty if you need the trigger to be generated by arbitrary artifacts.
Trigger Enabled
Must be checked for the trigger to activate.