SYSTEM Cited by 1 source
AWS CodePipeline¶
What it is¶
AWS CodePipeline is AWS's managed CI/CD-pipeline service — sourced by CodeCommit/GitHub/S3, building via CodeBuild (or arbitrary integrations), deploying via CloudFormation / StackSets / Elastic Beanstalk / CodeDeploy / custom actions. Pipelines are defined declaratively as ordered stages with parallel actions per stage; state is persisted in the pipeline.
Role in account-per-tenant platforms¶
In ProGlove's ~6,000-tenant platform, CodePipeline is the central orchestration point for fleet-wide CI/CD:
- One monorepo → one pipeline execution → one StackSet update operation → parallel deploys to thousands of tenant accounts via StackSets (Source: sources/2026-02-25-aws-6000-accounts-three-people-one-platform).
The pipeline lives in a central Infrastructure account; the StackSet administrator is that account; target accounts are the tenant accounts. This is the canonical patterns/fan-out-stackset-deployment topology.
Operational concerns at fan-out scale¶
- Pipeline duration is a function of target-account count. Large-scale updates "can take significant time to propagate."
- Partial failures surface as a failed stage — retry/rollback strategies have to be designed explicitly (Source: sources/2026-02-25-aws-6000-accounts-three-people-one-platform).
- Per-account pipeline parallelism competes with per-account quotas on CloudFormation and deployment services.
Stub page — full CI/CD-pipeline comparison (CodePipeline vs GitHub Actions vs Jenkins vs ArgoCD) is out of scope.
Seen in¶
- sources/2026-02-25-aws-6000-accounts-three-people-one-platform — central orchestrator of the CodePipeline + StackSets fan-out deployment at ProGlove Insight's scale.
Related¶
- systems/aws-stacksets — the fan-out deployment mechanism CodePipeline drives.
- systems/aws-cloudformation — the underlying IaC engine.
- concepts/account-per-tenant-isolation, patterns/fan-out-stackset-deployment.