The product that flows through the continuous delivery pipeline (potentially) brings in revenue and is seen as an investment. Sadly, some see the pipeline as an expenditure. Reality is that pipelines reflect hygiene (or the lack of it) and impact culture, productivity, and velocity of our teams. So let’s clear the air.

The continuous delivery pipeline is a product in its own right where scrum teams are the customers. The pipeline is a product that is built out of owned-and-operated, OSS (open source software), SaaS (software as a service), IaaS (infrastructure as a service) and PaaS (platform as a service) components. Pipelines need to be built, configured, deployed, tested and released just like other products.

Pipelines follow the services architecture and polyglot services make up the bulk of the functionality. Inspired by The Twelve-Factor App (details at https://12factor.net/), the Twelve-Factor Pipeline establishes the same gold standards for the pipeline application, as are applied to the products that flow through the pipeline. This talk goes into the heart of establishing the twelve factors to the design of pipelines.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.