CI/CD Agility and Controlling Pipeline Sprawl
summary
Claims that adequately sized resource classes, concurrent jobs, cautious caching and selective job processing cut pipeline time; sets a one-minute rule target per job to surface slow steps; diagnoses pipeline sprawl as YAML configs multiplying with a 1:1 repo-to-pipeline pattern and shows thousands of repeated aws s3 upload commands; fixes it by building reusable pipeline libraries and scripts (s3_upload.sh) and points to CircleCI orbs registry as a working example that centralizes changes and reduces vendor lock-in.
AI-written summary · about
chapters (19)
- 0:00Start
- 4:59Angel Rivera
- 6:14Pipelines at Scale
- 8:09Cicd Agility
- 9:19Pipeline Optimization
- 12:59Running Jobs Concurrently
- 17:04Selective Job Processing
- 19:26Conditional Conditional Job Execution
- 19:39Conditional Job Execution
- 20:52Setting Target Build Durations
- 23:48Caching
- 24:41Pipeline Sprawl
- 25:09Pipeline Config File
- 31:56Building a Pipeline Library
- 32:28Script Library
- 36:22Recap
- 41:03Identifying Patterns
- 41:55How Can Developers Establish a Better Adoption
- 43:03Principles of Continuous Integration
related talks
31mCI/CD Agility and Controlling Pipeline Sprawl
33mCI/CD Agility and Controlling Pipeline Sprawl Outline
20mCI/CD Agility and Controlling Pipeline Sprawl
32mPractical Tips & Tricks for CI/CD Success
26mFaster, Cheaper, Leaner: Horizontally Scaling a CI Pipeline
27mOptimizing CI/CD Pipelines for Faster Time to Market
51mCI/CD Patterns and Antipatterns - Things your Pipeline Should (Not) Do
21mBuild your JS Pipeline in Incremental Fashion