Project
Shared CI/CD workflows
Reusable GitHub Actions workflows and a standardised delivery path from build to Kubernetes, built for multiple teams.
What it is
A delivery setup built around shared, reusable GitHub Actions workflows: one standard way to build, test and deploy, used across multiple repositories and teams.
Why it exists
When every repository invents its own pipeline, delivery becomes inconsistent and hard to reason about. A shared set of workflows makes the common path standard and leaves teams to customise only where they actually need to.
How it works
- Reusable workflows define the standard build, test and publish steps.
- Container images are published to GHCR.
- Deployment follows a GitOps model with Argo CD rather than pipelines pushing directly to clusters.
- Runners are Kubernetes-based and isolated, so build jobs don’t share a host with anything important.
- Environments are separated, and secrets are handled per-environment.
Notes
- Build and deploy are kept deliberately distinct: CI produces artefacts, GitOps decides what runs.
Status
Active. Being refined and rolled out as the standard across repositories.