Dynamically create and store Spinnaker pipelines in a Git repo.
The Problem
Spinnaker’s UI is great for quickly building and running a pipeline. But with a UI-only approach, pipeline configs are not managed in source control like the rest of the code.
As a result, it is challenging to reuse, control, scale, and audit changes to your pipelines.
The Solution
Armory Pipelines as Code provides you with a GitOps-based deployment model for managing your pipelines. You can define your pipelines in JSON, HCL, or YAML, and automatically sync them from source control to Spinnaker.
A pipeline module’s library can be stored in a central repository for teams to reuse and contribute to, and you can validate your pipelines before committing them with the Armory CLI.
Pipelines As Code in 5 Minutes
Armory Sales Engineer Andrew Way demonstrates Pipelines As Code.
With Pipelines as Code, you get:
Pipeline version control in Git
For collaboration, reviews, audits, troubleshooting, and change management
Templated and modular pipelines and stages
Share best practices, reduce redundancy, and maintain pipeline consistency across your organization
Repeatable, scalable pipelines
Onboard your applications and your application developers quickly
Sophisticated features
Conditional logic, multiple repo / multiple branch support, Slack notifications, and more
Interested in learning more about
Armory Pipelines as Code
or Spinnaker?
