Back to Blog
DevOpsci-cdgithub-actionsargocd

The Evolution of Delivery: Mastering CI/CD in a Cloud-Native World

From Jenkins on a VM to GitHub Actions and ArgoCD — how CI/CD has changed, what modern best practices actually look like, and where teams still get it wrong in 2026.

Athar Shah11 min read5 February 2026

In 2018, CI/CD meant Jenkins. You had a server, it ran jobs, things occasionally caught fire and you restarted the server. It worked, mostly.

In 2026, CI/CD is distributed, ephemeral, and much more powerful — and much harder to reason about when something breaks.

The Three Eras of CI/CD

Era 1: The Jenkins Era (2010–2018) — Long-lived servers, shared build environments, XML config, slow feedback loops. But it worked and teams could reason about it.

Era 2: The SaaS Era (2018–2022) — CircleCI, Travis, GitHub Actions. Config as code, ephemeral runners, much faster. But secrets management became a problem and caching was tribal knowledge.

Era 3: Cloud-Native Delivery (2022–present) — GitOps with ArgoCD/Flux, container-native pipelines, OCI image signing, SLSA compliance. Powerful but complex.

What Modern CI/CD Should Look Like

Build fast. Anything over 5 minutes for a CI run is a problem. Use layer caching, parallelise tests, and split slow test suites.

Separate CI from CD. Your CI pipeline produces an artifact. Your CD pipeline deploys it. They should be separate workflows with separate access.

GitOps for Kubernetes. ArgoCD or Flux continuously reconciles your cluster state against Git. No kubectl apply in pipelines.

DORA metrics in your pipeline. Track deployment frequency, change failure rate, mean time to recovery. These are the metrics that matter.

Read the full guide with GitHub Actions workflow examples on Medium.

Need a team that can actually ship this?

NexForge combines AI development, product engineering, cloud delivery, and startup execution so ideas turn into production systems.