Continuous Deliveryon a modern web stack

Me• Web Developer for Mozilla Developer Network

• Tulsa Web Devs organizer

• Code for Tulsa organizer

• twitter.com/groovecoder

• Web Docs (HTML, CSS, JavaScript, DOM, etc.)

• wiki (python, django, javascript, and caffeine*)

• open source

• github.com/mozilla/kuma

Tulsa Web Devs• Local web developer community (494 members)

• tulsawebdevs.org

• on.fb.me/tulsawebdevs

• twitter.com/tulsawebdevs

• 36n.co (in January)

Code for Tulsa• Code for America brigade

• codefortulsa.org

• meetup.com/Code-for-Tulsa

• twitter.com/codefortulsa

Continuous Delivery

Why?

What is CD?

Continuous Deliveryat Mozilla Developer Network

i.e., on a Mozilla stack

Continuous Deliveryon a public, free web stack

github.com/codefortulsa/water-in-the-river

Stack

Version Control

try.github.io

Continuous Integration

https://guides.github.com/introduction/flow/index.html

with GitHub Flow

unit tests with mocha

Quality Gates: e.g., run unit tests on Travis

Quality Gate: run unit tests

e.g., run unit tests on Travis

Other Quality Gates

(Quick) QuestionsGitHub, GitHub Flow, Unit Tests, Travis CI

Production: master branch on heroku

Approval: Pull Requests deployed to Heroku

(Quick) QuestionsHeroku

Real-time Monitoring

Analytics

(Quick) QuestionsNew Relic & Google Analytics

Why all this?

Why not just build it? You know - be “lean”.

Total Time: 39 minutes

“Lean”: without code measuring data

“Lean”: with code measuring data

Thanks. Questions?

• @groovecoder, groovecoder.com

• @MozDevNet, developer.mozilla.org

• @tulsawebdevs, tulsawebdevs.org

• @codefortulsa, codefortulsa.org

• @36degreesN, 36n.co

GitHub, Travis CI, Heroku, New Relic, Google Analytics