I often work with customers who have several build and release pipelines that have been purpose-built for each application or service, and are typically sitting in the same repository as that application or service. Often these pipelines are extremely similar, and sometimes they are even the same as they have been copied and pasted between repositories. This can create a lot of overhead, duplication, and introduce inconsistency to your software development lifecycle.

A common principle of software development is "Don't Repeat Yourself", referred to as DRY, and in this wonderful world of all things 'DevOps', it's the responsibility of multiple parties to ensure DRY is used wherever possible, including pipelines. By bringing the DRY principle to CI/CD pipelines, you can lower the overhead, duplication, and management of pipelines to create centralised, abstracted, and reusable pipeline templates, which you can then call from multiple repositories.

Whether you're a Developer, Platform Engineer, Cloud Engineer, DevOps Engineer, Architect, or really anyone doing anything with CI/CD, you'll get value from this session by understanding the pain points of not incorporating DRY principles with pipelines, followed by the benefits of using pipeline templates for infrastructure or software deployments. While this talk will focus on GitHub Actions and their feature known as reusable workflows, the concepts and patterns apply to many different tools, so even if you aren't using GitHub for your CI/CD tooling today, you'll still be sure to get some value from the session.