Lightning Branches - A Way to Supercharge Your Feature Delivery
summary
Claims an opinionated workflow that gets small changes live fast by pushing every logical commit to a branch that auto-deploys. Uses git flow, Grunt, Travis CI, nginx, S3 and Chef so a git push builds artifacts and routes them to per-branch feature URLs. Frontend teams deploy about once or twice a day, create a Slack channel per feature for instant feedback, and report fewer meetings. The workflow actually runs at RedMart and delivers incremental features to production with low overhead.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:50Getting Code to Production Fast
- 1:28Real World Development Workflow of a Scaling Startup
- 9:55Huddling behind developers doesn't scale
- 12:02Empower multiple features development Git flow
- 13:34release - Combined features develop - Integration Branch feature/* - Development of Features based off develop branch
- 18:01Picks up branch (hence environment) - Runs tests - Create artifacts - Transfer artifacts to servers (based on environment) - Start application
- 19:29Deploy with Git! Don't mess with the developer workflow
- 22:11How do we actually deploy them?
related talks
46mContinuous Deployment Workflows
46mComic book continuity and Git rebase
39mOur journey from Gitflow to Trunk Based Development
58mFeature Branches And Toggles In A Post-GitHub World
30mPushing to master - adopting trunk based development
55mContinuous Deployment Workflows for Modern JavaScript
01h 00mReliability and speed by 'push to main' mentality
35mIncrease Agility and Quality Using Trunk-Based Development in Continuou...