Reusable CI/CD pipeline templates and the conventions behind them
A developer describes treating CI configuration as a shared library rather than copying pipelines into every new repository. The approach rests on a small set of templates covering 14 pipelines, governed by four rules: one workflow file per job, stable and descriptive job and artifact names, explicitly declared secrets, and cache keys tied to the lockfile hash. Example configurations are given for a matrix test workflow, a tag-triggered release, Dependabot updates, and a staging deploy that runs a migration dry run first. The author also outlines a GitLab-style staged pipeline that builds the artifact once and reuses it, with security stages such as container scanning and SBOM generation that fail on high-severity findings.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in