Upgrade to Pro — share decks privately, control downloads, hide ads and more …

From Code to Production

From Code to Production

Slides from my GRWebDev talk about how Modustri (http://modustri.com) uses GitHub, GDM (http://git-dependency-manager.info), Travis CI, Heroku and other tools to continuously ship software.

Eff2cdaa8474520ed29ebc38031fab87?s=128

Jace Browning

September 28, 2015
Tweet

Transcript

  1. From Code to Production @JaceBrowning

  2. None
  3. The Product

  4. None
  5. The Technology

  6. None
  7. The Tools

  8. None
  9. Continuous Integration / Deployment

  10. dev staging prod

  11. Feature Request ↓ Feature Branch

  12. None
  13. None
  14. feature/delete-machine-photo develop

  15. None
  16. $ make run $ make ci

  17. None
  18. None
  19. None
  20. Feature Branch ↓ Dev Deployment

  21. None
  22. None
  23. feature/delete-machine-photo develop

  24. None
  25. dev staging prod

  26. Dev Deployment ↓ Staging Deployment

  27. API iOS Web http://git-dependency-manager.info

  28. develop staging (all components)

  29. dev staging prod

  30. Bug Report ↓ Staging Deployment

  31. bug/fix-rotated-images staging

  32. (same GitHub + Travis CI as features)

  33. bug/fix-rotated-images staging

  34. Staging Deployment ↓ Production Deployment

  35. None
  36. staging master (all components)

  37. dev staging prod

  38. Summary • GitHub manages branches for in-work features • Travis

    CI reports build status to GitHub and Heroku • Heroku continuously deploys new features to dev • Groups of working features are promoted to staging • Bugs discovered in these features are fixed in staging • Product is be promoted to production on demand