Source: engineering.upside.com
Pipeliner: How Upside Manages Spinnaker Pipeline-TemplatesCategory: Kubernetes, automation, yaml
Here at Upside, our Site Reliability Engineering (SRE) team has gone all-in on Spinnaker for our software deployment strategy. As SREs, we’re responsible for our AWS cloud infrastructure, DevOps pipelines, and really just automating all the things.
Because one pipeline-template touches a lot of our microservices, we need to be sure that when we roll out new changes to these few pipeline-templates, that they work exactly as we intend.
We wanted to create YAML pipeline-template equivalents of our JSON pipeline-templates, and have Pipeliner “compile” the YAML version down into the JSON version, one that Spinnaker knows how to read.
When creating a new pipeline-template (that most likely has many of the same stages as other pipeline-templates), we simply create a new YAML pipeline-template, have it point to the appropriate config and stage files, and pass in the relevant variables.
Because one pipeline-template touches a lot of our microservices, we need to be sure that when we roll out new changes to these few pipeline-templates, that they work exactly as we intend.
We wanted to create YAML pipeline-template equivalents of our JSON pipeline-templates, and have Pipeliner “compile” the YAML version down into the JSON version, one that Spinnaker knows how to read.
When creating a new pipeline-template (that most likely has many of the same stages as other pipeline-templates), we simply create a new YAML pipeline-template, have it point to the appropriate config and stage files, and pass in the relevant variables.
Related Articles
Community Partners
DevOps Careers