Increase Agility and Quality Using Trunk-Based Development in Continuou...
summary
Claims that moving to trunk-based development cuts time to ship and raises quality by keeping main always deployable, with teams committing multiple times per day and CI that auto-detects failures and rolls back. Examples: migration from Git Flow/GitHub Flow, use of short-lived preview environments, Helm-deployed full-stack PR apps, and feature flags and canary rollouts. Early months show many breakages on small pilot teams (8–10 people) but ultimately faster, more frequent deliveries across ~100 engineers.
AI-written summary · about
chapters (12)
- 0:00Introduction and session overview
- 1:46Branching strategies overview
- 5:14Current adoption of trunk-based development
- 9:58Objections and challenges to trunk-based development
- 12:28Handling large changes and rollbacks
- 17:51Benefits of trunk-based development
- 21:01Tooling and process challenges
- 24:39Team experiences and observations
- 26:07Practical advice and lessons learned
- 30:17Pull request and approval processes
- 33:30Preview environments for PRs
- 34:34Closing remarks and Q&A
related talks
39mOur journey from Gitflow to Trunk Based Development
30mPushing to master - adopting trunk based development
18mTrunk Based Development and Feature Toggles
45mContinuous Integration: That’s Not What They Meant
11mCreate unfair competitive advantage w/CI/CD Pipelines
01h 01mA team's transition to Continuous Delivery
46mContinuous Deployment Workflows
46mHow to architect for continuous delivery?