Pipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
summary
Lists seven real antipatterns with concrete fixes: avoid the ritual of running full builds on PR, merge and nightly; use a GitHub Actions YAML pre-step (path-filter) to skip unrelated front-end or backend jobs; stop hoarding 7,000 Docker images (many with ~211 downloads) and prune old artifacts; reorder slow integration tests earlier to fail fast (saves ~4 minutes); split a 24m40s monolithic pipeline into parallel pipelines plus artifact publishing to regain ~8 minutes; prefer calling tools (cargo, dotnet) over wrapper tasks; cache build output and tooling images to shave minutes (examples: cargo install 6m → 8s).
AI-written summary · about
chapters (13)
- 0:00Pipeline challenges intro
- 2:27Why patterns matter
- 3:08Antipattern one: ritual
- 5:38Pattern two: conditional steps
- 8:51Antipattern two: hoarding artifacts
- 10:16Antipattern three: aesthetic order
- 12:22Antipattern four: one pipeline trap
- 15:39Antipattern five: gift-wrapped tasks
- 17:25Antipattern six: complex pipelines
- 19:35Antipattern six: platform entanglement
- 20:59Pattern seven: caching
- 24:57Tooling images for faster builds
- 26:20Summary
related talks
54mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
51mCI/CD Patterns and Antipatterns - Things your Pipeline Should (Not) Do
41mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
25mHow NOT to Build a Pipeline
46mContinuous delivery antipatterns
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
18mDesign Patterns For Efficient DevOps Processes
27mOptimizing CI/CD Pipelines for Faster Time to Market