How NOT to Build a Pipeline
summary
Talk demonstrates concrete Concourse failures and fixes: misconfigured git creds hit GitHub API limits, tests silently pass because tasks don’t fail, bash scripts delete things unless set -euo pipefail and ShellCheck are used, missing logs force container interception, flaky network failures hide real bugs, accidental double-building of Docker images causes untested releases, S3 bucket leaks exhaust quotas, and unordered/over-wired jobs break flows. Fixes: use past + trigger constraints, represent external state with the pool resource, use input/output mapping and make tasks idempotent so pipelines reliably promote the exact artifact you tested.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:44Build anti-patterns
- 12:10Flow anti-patterns
- 23:16Fixing pipeline issues
- 23:39Summary and resources
related talks
37mIs Your Approach to Pipeline Security Flawed? Rethinking CI/CD Security
27mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
28m"Who tests the testers? Making and testing pipelines"
10mIt's Time We Start Securing Our CICD Pipelines
51mCI/CD Patterns and Antipatterns - Things your Pipeline Should (Not) Do
01h 01mCleaning the Sewage out of your DevOps Pipeline
47mCI/CD Agility and Controlling Pipeline Sprawl
21mStrategies for Testing Your Pipeline