CI/CD Platform Engineering

Designing and Operating Enterprise Build, Release, and Deployment Platforms

Goal: Learn how to build a CI/CD Platform that enables engineering teams through standardized, secure, scalable, and self-service software delivery. This book focuses on platform architecture, release engineering, pipeline governance, progressive delivery, and developer experience, rather than a single CI/CD product. GitHub Actions, Argo Workflows, Tekton, Jenkins, and other tools are presented as implementations of common platform patterns.

If this were a book, this page is the table of contents. Each Part below is a chapter; each chapter links out to the concepts, designs, and platform notes that already exist elsewhere in this wiki instead of duplicating them. Unwritten chapters are listed with a — _(stub)_ marker, not empty files.

Parts

00 — Introduction to CI/CD Platform Engineering

Frames CI/CD as a platform product rather than a pipeline tool, lays out the seven-layer reference architecture used throughout the book, and introduces the five-stage delivery maturity model.

1 — The Evolution of Software Delivery — (stub)
2 — What Is a CI/CD Platform? — (stub)
3 — CI/CD Platform Architecture — (stub)
4 — Platform Maturity Model — (stub)

01 — Source Control & Pipeline Foundations

Covers Git as the platform backbone and the architectural and design principles pipelines are built on before any specific tool enters the picture. See What is GitOps for the pattern underlying build-once-deploy-many referenced from the GitHub Actions design-patterns chapter below.

1 — Git as the Platform Backbone — (stub)
2 — Pipeline Architecture — (stub)
3 — Pipeline Design Principles — (stub)
4 — Pipeline Lifecycle — (stub)
5 — GitHub Actions: CI/CD Design Patterns — (stub)

02 — Build Platform

Covers the architecture, optimization, standardization, and reliability of the build layer — where source becomes a testable, deployable unit.

1 — Build Platform Architecture — (stub)
2 — Build Optimization — (stub)
3 — Build Standardization — (stub)
4 — Build Reliability — (stub)
5 — GitHub Actions: Cache Optimization — (stub)
6 — GitHub Actions: Pipeline Performance — (stub)

03 — Continuous Integration Platform

Covers CI orchestration patterns, the automated testing platform, code quality gates, and security scanning built into the CI stage. Grounded partly in this repo’s own Code Standards.

1 — CI Architecture — (stub)
2 — Automated Testing Platform — (stub)
3 — Code Quality Platform — (stub)
4 — Security in CI — (stub)
5 — GitHub Actions: Performance Engineering — (stub)

04 — Artifact Platform

Covers artifact management, lifecycle, and dependency governance. See Software Supply Chain Security for the Sigstore/cosign/SLSA implementation detail behind the Software Supply Chain chapter below.

1 — Artifact Management — (stub)
2 — Artifact Lifecycle — (stub)
3 — Software Supply Chain — (stub)
4 — Dependency Management — (stub)
5 — GitHub Actions: Artifacts — (stub)

05 — Continuous Delivery Platform

Covers deployment architecture, environment management, and deployment/progressive-delivery strategies. See GitOps, ArgoCD, and FluxCD for GitOps tool mechanics referenced from the Deployment Architecture chapter below.

06 — GitHub Actions Platform

The deepest Part in this book — GitHub Actions examined end to end as one concrete implementation of the platform patterns from Parts 00–05: workflow syntax and execution model, building and composing pipelines, reusable automation, self-hosted runner infrastructure, monorepo/enterprise- scale automation, and integration with each major cloud. This repo’s own .github/workflows/reusable-docker.yml, reusable-dotnet.yml, reusable-python.yml, and reusable-terraform.yml are working workflow_call examples behind the Reusable Workflows / Composite Actions / Workflow Templates chapters; deploy-with-gates.yml and services-from-metadata.yml / services-integration-from-metadata.yml ground the Monorepo Pipelines and Large-Scale Repository Automation chapters. See AKS for the runner-hosting fleet architecture behind the Runners chapters, and AKS, EKS, GKE, Helm, Kustomize, Argo CD, and Flux for the deploy-target tradeoffs behind the Cloud Integrations chapters. GitHub-Actions-specific authentication, secrets, and secure-pipeline mechanics live in Part 09 rather than being duplicated here; GH-200 certification prep and quick-reference material live in Part 15.

1 — Why GitHub Actions — (stub)
2 — GitHub Actions Architecture — (stub)
3 — YAML Essentials — (stub)
4 — Workflow Syntax — (stub)
5 — Events & Triggers — (stub)
6 — Expressions & Contexts — (stub)
7 — Running Jobs — (stub)
8 — Matrix Builds — (stub)
9 — Workflow Outputs — (stub)
10 — Reusable Workflows — (stub)
11 — Composite Actions — (stub)
12 — Workflow Templates — (stub)
13 — GitHub-Hosted Runners — (stub)
14 — Self-Hosted Runners — (stub)
15 — Actions Runner Controller (ARC) — (stub)
16 — Monorepo Pipelines — (stub)
17 — Large-Scale Repository Automation — (stub)
18 — Azure — (stub)
19 — AWS — (stub)
20 — Google Cloud — (stub)
21 — Containers — (stub)
22 — Kubernetes — (stub)

07 — Workflow Orchestration Platforms

Covers Argo Workflows, Tekton, and Jenkins as Kubernetes-native and classic orchestration engines, and how to choose among them. (Argo Workflows here is examined as CI/CD build orchestration — see data-engineering/06-workflow-orchestration for orchestrators used in data-pipeline contexts.)

1 — Argo Workflows — (stub)
2 — Tekton — (stub)
3 — Jenkins Platform — (stub)
4 — Choosing the Right Platform — (stub)

08 — Release Engineering

Covers release lifecycle, automation, governance, and observability. See platform-engineering-fundamentals’ DORA metrics chapter for the KPI definitions behind the Release Observability chapter below.

1 — Release Engineering Fundamentals — (stub)
2 — Release Automation — (stub)
3 — Deployment Governance — (stub)
4 — Release Observability — (stub)

09 — Platform Security

Covers identity, secrets, policy-as-code, secure pipeline design, supply chain security, and compliance automation as the security layer spanning every earlier Part. GitHub-Actions-specific authentication (OIDC to cloud), secrets management, and secure-pipeline mechanics (chapters 7–9) implement these generic controls concretely — see Identity: OAuth, OIDC, JWT, SPIFFE, mTLS, Authentication Patterns, Secure Communication Patterns, and Software Supply Chain Security for the underlying identity/pattern/supply-chain foundations these three chapters build on rather than re-derive.

1 — Identity & Access Management — (stub)
2 — Secret Management — (stub)
3 — Policy as Code — (stub)
4 — Secure Pipeline Design — (stub)
5 — Software Supply Chain Security — (stub)
6 — Compliance Automation — (stub)
7 — GitHub Actions: Authentication — (stub)
8 — GitHub Actions: Secrets Management — (stub)
9 — GitHub Actions: Secure Pipelines — (stub)

10 — Platform Observability

Covers pipeline metrics, logging, tracing, dashboards, and delivery SLOs — treating the CI/CD platform itself as a system worth observing. GitHub-Actions-specific notification routing and failure analysis (chapters 6–7) apply the general alert-routing model in Alerting & Routing to workflow run events specifically.

1 — Pipeline Metrics — (stub)
2 — CI/CD Logging — (stub)
3 — Pipeline Tracing — (stub)
4 — CI/CD Dashboards — (stub)
5 — Delivery SLOs — (stub)
6 — GitHub Actions: Notifications — (stub)
7 — GitHub Actions: Failure Analysis — (stub)

11 — Reliability Engineering for CI/CD

Covers high availability, scaling, disaster recovery, capacity planning, and incident response for the CI/CD control plane itself.

1 — High Availability — (stub)
2 — Scaling Pipeline Platforms — (stub)
3 — Disaster Recovery — (stub)
4 — Platform Capacity Planning — (stub)
5 — Incident Response — (stub)

12 — Enterprise CI/CD Platforms

Covers multi-cloud, multi-region, and multi-tenant delivery, plus the governance, cost, and developer-experience concerns that show up only at enterprise scale. GitHub-Actions-specific cost optimization (chapter 7) is the tool-level counterpart to the Platform Cost Engineering chapter above.

1 — Multi-Cloud Delivery — (stub)
2 — Multi-Region Deployments — (stub)
3 — Multi-Tenant Pipeline Platforms — (stub)
4 — Platform Governance — (stub)
5 — Platform Cost Engineering — (stub)
6 — Developer Experience — (stub)
7 — GitHub Actions: Cost Optimization — (stub)

13 — CI/CD Platform Anti-Patterns

Catalogs the failure modes a platform team runs into repeatedly — sprawl, copy-paste pipelines, manual releases, shared credentials, unbounded pipeline growth, missing standards, and missing observability.

1 — Pipeline Sprawl — (stub)
2 — Copy-Paste Pipelines — (stub)
3 — Manual Releases — (stub)
4 — Shared Credentials — (stub)
5 — Long-Running Pipelines — (stub)
6 — Lack of Standardization — (stub)
7 — Ignoring Pipeline Observability — (stub)

14 — MAANG Interview Preparation

Applies the whole book to Staff/Principal (L6/L7) platform engineering interviews — including GitHub-Actions-specific interview questions and enterprise scenarios (chapters 4, 7–8). See system-design’s CI/CD platform case study referenced from the first chapter below, plus Secrets Manager and Build vs. Buy for the case studies the GitHub Actions interview chapters frame follow-ups around.

1 — CI/CD Platform System Design — (stub)
2 — Designing Enterprise Build Platforms — (stub)
3 — Progressive Delivery Design — (stub)
4 — GitHub Actions Interview Questions — (stub)
5 — Release Engineering Case Studies — (stub)
6 — Staff/Principal Platform Engineering Scenarios — (stub)
7 — GitHub Actions: Enterprise Scenarios — (stub)
8 — GitHub Actions: Case Studies — (stub)

15 — Appendices

Quick-reference material — reference architecture, tool comparison matrices, decision matrices, a supply-chain security checklist, DORA metrics, the maturity model recap, and a full set of GitHub-Actions-specific references and certification-prep material (chapters 8–19) — for lookup after working through the chapters above.

1 — CI/CD Platform Reference Architecture — (stub)
2 — GitHub Actions: Migration Guide — (stub)
3 — Argo Workflows & Tekton Comparison Matrix — (stub)
4 — Progressive Delivery Decision Matrix — (stub)
5 — Software Supply Chain Security Checklist (SLSA, SBOM, Sigstore) — (stub)
6 — DORA Metrics & Delivery KPIs — (stub)
7 — CI/CD Platform Maturity Model — (stub)
8 — GH-200 Exam Objectives — (stub)
9 — GitHub Actions: Hands-on Labs — (stub)
10 — GH-200 Practice Exams — (stub)
11 — GitHub Actions: Troubleshooting Playbook — (stub)
12 — GitHub Actions: YAML Reference — (stub)
13 — GitHub Actions Expression Cheat Sheet — (stub)
14 — GitHub Actions: Context Reference — (stub)
15 — Marketplace Best Practices — (stub)
16 — GitHub CLI (gh) Reference — (stub)
17 — GitHub Actions: Common Error Messages — (stub)
18 — GH-200 Exam Checklist — (stub)
19 — GitHub Actions: MAANG Interview Checklist — (stub)

Learning Outcomes

After completing this book, you will be able to:

Design a CI/CD Platform that supports self-service software delivery at enterprise scale.
Build standardized Pipeline-as-Code frameworks with reusable templates, workflow libraries, and governance controls.
Architect resilient build systems, artifact repositories, deployment pipelines, and progressive delivery mechanisms.
Operate enterprise-grade GitHub Actions, Argo Workflows, Tekton, and Jenkins platforms, selecting the appropriate tool based on organizational requirements.
Implement secure software supply chains using SBOMs, artifact signing, SLSA, OIDC, and policy-driven controls.
Measure and optimize delivery performance using DORA metrics, pipeline observability, release engineering metrics, and developer experience indicators.
Evaluate architectural trade-offs and confidently discuss enterprise CI/CD platform designs in MAANG Staff/Principal (L6/L7) platform engineering and system design interviews.

Metadata


Author	Amit Singh
Scope	ci-cd