Continuous Deployment Workflows for Modern JavaScript
summary
Describes a working continuous delivery pipeline used across client projects: Git-based workflows with the magic of rebasing and single commit per pull request, Jenkins for CI, Mocha/Karma tests, Grunt/Bower/npm/yo for builds, Vagrant/Fabric for reproducible staging, and Git submodules to share deployment scripts. Targets include deploying small, atomic features and being able to deploy in under an hour and roll back in minutes. Notes a six-hour outage from OS/Perl mismatch that automation later eliminates and outlines a phase model (phase 1: 3–6 months; phase 2: 6+ months).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:26Lean manufacturing in software
- 8:19Waste reduction and improvement
- 13:54Continuous deployment evolution
- 25:29Phase one maturity
- 33:09Phase two workflows
- 41:21JavaScript stack tools
- 47:37Frontend architecture testability
- 51:52Resources and closing
related talks
12mContinuous Deployment in a heavily regulated environment
30mModern Continuous Delivery
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
46mComic book continuity and Git rebase
33mSoftware development practices for companies that want to make an impact
05mGit as a continuous manager
28mContinuous everything: Moving to DevOps on AWS
50mWhy You Need a Software Delivery Machine