Spinnaker Operations: Difference between revisions
Jump to navigation
Jump to search
Line 38: | Line 38: | ||
===Create a Pipeline from Template=== | ===Create a Pipeline from Template=== | ||
{{Internal|Spinnaker Create a Pipeline from Template#Overview|Create a Pipeline from Template}} | {{Internal|Spinnaker Create a Pipeline from Template#Overview|Create a Pipeline from Template}} | ||
=Executing a Pipeline= | ==Executing a Pipeline== | ||
==Executing a Pipeline in Command Line== | ===Executing a Pipeline in Command Line=== | ||
{{Internal|Spinnaker Executing a Pipeline in Command Line#Overview|Executing a Pipeline in Command Line}} | {{Internal|Spinnaker Executing a Pipeline in Command Line#Overview|Executing a Pipeline in Command Line}} | ||
Line 84: | Line 84: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
* If necessary, copy the content of "parameterConfig" and paste. | * If necessary, copy the content of "parameterConfig" and paste. | ||
=Pipeline Template Operations= | =Pipeline Template Operations= | ||
{{Internal|Spinnaker Pipeline Template Operations|Pipeline Template Operations}} | {{Internal|Spinnaker Pipeline Template Operations|Pipeline Template Operations}} |
Revision as of 23:56, 30 May 2023
Internal
CLI Access
Installation and Configuration
curl -LO https://storage.googleapis.com/spinnaker-artifacts/spin/$(curl -s https://storage.googleapis.com/spinnaker-artifacts/spin/latest)/darwin/amd64/spin
chmod +x spin
sudo mv spin /usr/local/bin/spin
Follow specific configuration instructions depending on the authentication method against the backend.
Options
-k|--insecure
Ignore certificate errors.
Operations
spin -k application list
Application Operations
Create an Application
Configure an Application
Pipeline Operations
List Pipelines
spin [-k] pipeline list --application my-application
Create a Pipeline
Create a Pipeline from the UI
Create a Pipeline from Template
Executing a Pipeline
Executing a Pipeline in Command Line
Delete a Pipeline
spin pipeline delete --name my-pipeline --application my-application
Insert a Stage into an Existing Pipeline
Use the JSON representation. Select the pipeline → Pipeline Actions → Edit as JSON → identity "stages" and introduce the JSON representation of the stage.
Update the refId
, otherwise you'll get "Error: The refId property must be unique across stages. Duplicate id(s): 5".
Also update the requisiteStageRefIds
, otherwise you'll get the stage inserted after the wrong stage.
Update the requisiteStageRefIds
of the stage that follows.
{
"name": "BreakPoint",
"refId": "5",
"requisiteStageRefIds": [
"4"
],
},
Copy and Paste a Pipeline as JSON
- Create an empty pipeline.
- Go to the source pipeline → Configure → Pipeline Actions → Edit as JSON
- Copy the content of "stages" and paste.
- Update stages accordingly.
- ⚠️ Search for "moniker" and replace the value with the value of the application name:
{
[...]
"stages": [
{
[...]
"moniker": {
"app": "my-app-name"
},
[...]
]
}
- If necessary, copy the content of "parameterConfig" and paste.
Pipeline Template Operations
Blue-Green Deployments with Spinnaker
Running an Arbitrary Script
Log Management
TO INVESTIGATE: