Develop Pipelines as Code
summary
Adopts Armory Pipelines as Code with pipeline JSON stored in a mono GitHub repo, synced by a Dinghy service that diffs commits and applies changes to Spinnaker. Builds reusable shareable stage modules (bake, create namespace, deploy manifest, docker-registry triggers, run-script) parameterized per env (dev, staging, RC, production). Enforces change control via pull‑request validation, designated merge groups and LDAP‑based RBAC so only approved users can modify or trigger pipelines.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:28Background
- 3:59Pipeline School
- 7:36Pipeline UI
- 9:03Pipeline Code
- 9:59Pipeline Modules
- 12:08Override Values
- 14:16Docker Registry
- 15:02Run Script
- 15:52Enable Change Control
- 16:31Improve Share Modules
- 18:28Conclusion
related talks
45mBecoming a Plumber: Building Deployment Pipelines
25mBuilding Universal CI/CD Pipelines
34mFrom Code to Deployment: A Deep Dive into Pipelines as Code
23mBuilding Secure Package Pipelines
20mMulti-Stage Deployment Pipelines the GitOps Way
20mCI/CD Agility and Controlling Pipeline Sprawl
43mAll Aboard: Transforming Software Delivery Using Spinnaker
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers