An Overview of Managed Pipeline Templates V2
summary
Managed Pipeline Templates V2 replaces server-side composition with a local JSON-it build step using spawn it, then pushes versioned templates into Front50 with spin CLI via a CI job (Cloud Build + Cloud Source). Hydration merges template variables and stages at execution, templates support tags like stable/experimental and pinning by digest, UI shows templated pipelines; demo builds an image, saves a template (pipeline templates save succeeded) and deploys the blue “Hello Spinnaker Summit” update.
AI-written summary · about
chapters (12)
- 0:00Introduction to pipelines
- 1:33Pipeline templates overview
- 4:26Template hydration process
- 6:36Value of managed templates
- 9:25Evolution from v1 to v2
- 11:52Implementation demo
- 19:53CI and CLI automation
- 23:20UI and pipeline workflows
- 27:05Versioning and tags
- 30:16Community and roadmap
- 32:35Managed delivery vs templates
- 34:48Q&A session
related talks
29mKickstarting Your Azure Pipeline with Templates
20mDevelop Pipelines as Code
26mSpinnaker Summit
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
31mManaged Releases with Spinnaker
31mSmart Control Plane for CICD Pipelines
50mSpinnaker get control over your deployements
35mBuilding Reusable DevSecOps Pipelines on a Secure Kubernetes Platform