Spinnaker Create a Deployment Pipeline from UI: Difference between revisions
Jump to navigation
Jump to search
m (Ovidiu moved page Spinnaker Create a Deployment Pipeline to Spinnaker Create a Deployment Pipeline from UI without leaving a redirect) |
|||
| (24 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
=Overview= | =Overview= | ||
This article describes the mechanics of creating a deployment pipeline aimed at performing deployments into a Kubernetes cluster. Also see: {{Internal| | This article describes the mechanics of creating a deployment pipeline aimed at performing deployments into a Kubernetes cluster, with the Spinnaker UI. Also see: {{Internal|Spinnaker_Pipeline#Overview|Spinnaker Pipeline}} | ||
= | =<span id='Pipeline_Creation'></span>Pipeline Creation from UI= | ||
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. | 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 | '''Type''': Pipeline | ||
Pipeline Name: | '''Pipeline Name''': The pipeline name cannot contain any of the following characters: / \ ? % # | ||
'''Copy From''': | '''Copy From''': See [[#Pipeline_Creation_by_Copying_it_from_Another_Pipeline|Pipeline Creation by Copying it from Another Pipeline]] below. | ||
==Pipeline Configuration | ==Pipeline Creation by Copying it from Another Pipeline== | ||
Specify another pipeline in the same Application. | |||
=Pipeline Configuration= | |||
The pipeline configuration allows setting the following elements: | The pipeline configuration allows setting the following elements: | ||
==Execution Options== | |||
* [[Spinnaker_Concepts#Disable_concurrent_pipeline_executions_.28only_run_one_at_a_time.29|Disable concurrent pipeline executions (only run one at a time)]]. Set by default. | * [[Spinnaker_Concepts#Disable_concurrent_pipeline_executions_.28only_run_one_at_a_time.29|Disable concurrent pipeline executions (only run one at a time)]]. Set by default. | ||
* [[Spinnaker_Concepts#Do_not_automatically_cancel_pipelines_waiting_in_queue|Do not automatically cancel pipelines waiting in queue]] | * [[Spinnaker_Concepts#Do_not_automatically_cancel_pipelines_waiting_in_queue|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. | All triggers require specifying permissions, which are the OD groups under whose identity the pipeline will operate when triggered. | ||
===Trigger Types=== | |||
====Docker Registry Trigger==== | ====Docker Registry Trigger==== | ||
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|Spinnaker_Concepts#Helm_Chart_Trigger|Helm Chart Trigger}} | For configuration, see: {{Internal|Spinnaker_Concepts#Helm_Chart_Trigger|Helm Chart Trigger}} | ||
====GitHub Trigger==== | |||
==== | For configuration, see: {{Internal|Spinnaker_Concepts#GitHub_Trigger|GitHub Trigger}} | ||
===Artifact Constraints=== | |||
====Trigger Enabled | See {{Internal|Spinnaker_Concepts#Artifact_Constraints|Artifact Constraints}} | ||
===Trigger Enabled=== | |||
Must be checked for the trigger to activate. | Must be checked for the trigger to activate. | ||
==Parameters== | |||
==Notifications== | |||
==Metadata== | |||
=Stages= | |||
Add stage. | |||
= | ==Render Helm== | ||
==Helm | Renders a Helm manifest. | ||
{{Internal|Spinnaker_Stage_Bake_(Manifest)#Overview|Bake (Manifest)}} | |||
==Deploy Helm== | |||
Used to deploy Helm charts previously rendered by [[Spinnaker_Stage_Bake_(Manifest)#Overview|Bake (Manifest)]]. | |||
{{Internal|Spinnaker_Stage_Deploy_(Manifest)#Overview|Deploy (Manifest)}} | |||
= | ==Manual Judgement== | ||
{{Internal|Spinnaker_Concepts#Manual_Judgement|Manual Judgement}} | |||
=End State= | |||
After a successful deployment, the application will be populated with the associated "cluster", "server group" and "load balancer". | |||
Latest revision as of 03:34, 31 May 2023
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, with the Spinnaker UI. Also see:
Pipeline Creation from UI
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: The pipeline name cannot contain any of the following characters: / \ ? % #
Copy From: See Pipeline Creation by Copying it from Another Pipeline below.
Pipeline Creation by Copying it from Another Pipeline
Specify another pipeline in the same Application.
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.
Trigger Types
Docker Registry Trigger
For configuration, see:
Helm Chart Trigger
For configuration, see:
GitHub Trigger
For configuration, see:
Artifact Constraints
See
Trigger Enabled
Must be checked for the trigger to activate.
Parameters
Notifications
Metadata
Stages
Add stage.
Render Helm
Renders a Helm manifest.
Deploy Helm
Used to deploy Helm charts previously rendered by Bake (Manifest).
Manual Judgement
End State
After a successful deployment, the application will be populated with the associated "cluster", "server group" and "load balancer".