CI/CD Patterns and Antipatterns - Things your Pipeline Should (Not) Do
summary
Lists concrete CI/CD antipatterns and exact fixes: use a pre-step to detect changed paths and run conditional pipeline steps so backend tests skip pure frontend PRs; split one 25‑minute monolith into parallel jobs to cut feedback to ~12 minutes by split into parallel pipelines; cache build outputs to shave ~4–5 minutes and use Docker BuildKit cache to save ~6 minutes; delete old artifacts weekly to avoid hoarding; call CLIs directly instead of wrapper actions; move complex logic into Make scripts and use tooling images with unique tags to avoid interference.
AI-written summary · about
chapters (17)
- 0:00CI/CD patterns intro
- 2:32Anti-pattern 1: The ritual
- 10:23Anti-pattern 2: Hoarding artifacts
- 12:50Anti-pattern 3: Natural ordering trap
- 15:19Anti-pattern 4: One pipeline to rule
- 20:23Anti-pattern 5: Wrapper tasks
- 23:55Anti-pattern 6: Complicated pipelines
- 28:06Anti-pattern 6.5: Tangled pipeline code
- 31:42Anti-pattern 7: Fresh builds
- 33:45Anti-pattern 7: Caching dependencies
- 39:26Anti-pattern 8: Tooling images
- 41:54Anti-pattern 8: Shared environment interference
- 42:37Anti-pattern 9: Underpowered agents
- 44:26Running own build agents pros and cons
- 47:40Future CI tools overview
- 49:28Recap of antipatterns
- 50:17Q&A
related talks
27mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
41mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
32mPractical Tips & Tricks for CI/CD Success
47mCI/CD Agility and Controlling Pipeline Sprawl
31mCI/CD Agility and Controlling Pipeline Sprawl
27mOptimizing CI/CD Pipelines for Faster Time to Market
25mHow NOT to Build a Pipeline
01h 02mContinuous Integration: Tips & Tricks