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

Boston I/O: Continuous Integration

Boston I/O: Continuous Integration

Continuous Integration is about more than just testing. It is a crucial tool for constantly producing shippable code, reducing the time it takes to deploy new releases and forming a basis for stable software and happy users. In this brief presentation we will look at the how and why.

5c2b452f6eea4a6d84c105ebd971d2a4?s=128

Konstantin Haase

February 15, 2014
Tweet

Transcript

  1. Continuous Integration (spoiler alert)

  2. None
  3. no product product write code

  4. 1.0 write X 2.0 write Y 3.0

  5. 1.0 write X 2.0 write Y 3.0 Does X still

    work in 3.0?
  6. None
  7. 1.0 write X 2.0 write Y

  8. None
  9. 1.0 write X integration write Y 2.0

  10. None
  11. None
  12. None
  13. None
  14. 1.0 write X integration write Y 2.0 Does X still

    work? It does!
  15. Happy Developers

  16. Happy Users

  17. 1.0 integration 2.0

  18. Sad Developers

  19. 1.0 integration 2.0

  20. Sad Users

  21. 1.0 2.0 CI CI CI Putting the C in CI

  22. Happy Developers

  23. A Culture Of Shipping

  24. None
  25. None
  26. release early, release often

  27. Happy Users

  28. automation is the key

  29. Travis CI Jenkins

  30. None
  31. None
  32. None
  33. None
  34. Oh no, master is broken!

  35. None
  36. None
  37. None
  38. None
  39. None
  40. None
  41. automate integrate ship it

  42. Questions? ! me@rkh.im @konstantinhaase