(A talk given at PIPELINE Conference – March 2018 – What if you treat your CI pipeline as a product?  – https://pipelineconf.info/speakers/)

“There are many tools that facilitate a “CI as Code” approach to continuous delivery, but how many organisations are treating their CI infrastructure as an internally-facing product? Our software team has taken “CI as Code” quite literally over the last two years, as a dedicated team has developed a highly-configurable template for a Concourse pipeline. This template features opinionated APIs and useful abstractions that enable product teams to build, test, and ship open-sourced releases as well as artefacts for enterprise platform users. This talk will be equal parts experience report and cautionary tale: We’ll share the technical and cultural challenges of shared infrastructure templates from the perspectives of both producer and consumer, and we’ll make some recommendations about when and how you should consider implementing this pattern in your organisation. When your pipelines are code, it needs love just like everything else you ship!”

Denise currently works as a full-time open source Cloud Foundry contributor on the Services API team, whose role is to define a standard specification for provisioning services on the platform. Prior to joining Pivotal she wrote web applications for a financial publishing company and worked at an educational technology startup. In her spare time, she enjoys traveling, playing classical guitar, and being a mediocre skier.

Mark joined Pivotal Cloud Foundry as a software engineer in September 2016. At Pivotal, he anchored a project to provide a generic best practice CI Pipeline-as-a-product to support teams who deliver data services to open source Cloud Foundry users and enterprise platform customers. Currently he is working on RabbitMQ for PCF. He speaks fluent YAML and Concourse.