Our journey from Gitflow to Trunk Based Development
summary
Company moves from Gitflow to Trunk Based Development, drops long‑living branches and makes every trunk commit a deployable unit, uses Jenkins + Kubernetes to spin ephemeral feature environments per branch with dynamic URLs tied to Jira IDs, and wraps unfinished work in feature flags (custom or SaaS) so deployment and release are decoupled. Team goes from one‑hour releases with five devs to peak 13 deployments in one week and top day 6 deployments, sees a 7% defect rate, and removes merge bottlenecks while improving developer ownership.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:13Branching strategy
- 4:14Summary of Gitflow
- 6:55Continuous Integration
- 9:11Trunk Based Development
- 11:13How to Implement
- 16:16Feature Flags
- 24:32Future Flags
- 34:44Summary
related talks
35mIncrease Agility and Quality Using Trunk-Based Development in Continuou...
30mPushing to master - adopting trunk based development
18mTrunk Based Development and Feature Toggles
58mFeature Branches And Toggles In A Post-GitHub World
01h 01mA team's transition to Continuous Delivery
26mLightning Branches - A Way to Supercharge Your Feature Delivery
39mOur journey to automated releases
46mContinuous Deployment Workflows