26 Feature Branches and other tales from the wild
summary
A client runs 26 feature branches and only notices integration failures after sprint-end, so the CI server rarely sees combined changes; another team deploys the latest artifact for nine months instead of the one that passed the pipeline. Automated dependency scanning shows over 20% of Maven Central projects pull libraries with critical vulnerabilities. Teams promise 12 minute deploys but skip compliance. Advice: prefer trunk based development, tag and promote artifacts through stages, treat security as everyone’s job, and use Kubernetes only when you actually need it.
AI-written summary · about
related talks
58mFeature Branches And Toggles In A Post-GitHub World
37mKeep Your Dependencies in Check
39mOur journey from Gitflow to Trunk Based Development
50mFeature Branching considered Evil
41mContinuous delivery in 10 easy mistakes
40mContinuous Delivery Anti-Patterns
01h 06mWaltzing with Branches
38mContinuous Integration May Have Negative Effects