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

Continuous Delivery – A GitHub Story

Continuous Delivery – A GitHub Story

A presentation delivered by Matthew McCullough at DevNexus 2013 in Atlanta, GA, USA.

Bededa744012c87721d68f69342f81b0?s=128

Matthew McCullough

February 19, 2013
Tweet

Transcript

  1. a GitHub Story CONTINUOUS D E L I V E

    R Y
  2. matthew@github.com github.com/training @matthewmccull matthewmccullough

  3. None
  4. None
  5. Probably the most important technical book of 2010 -Martin Fowler,

    ThoughtWorks
  6. Why? The current state of affairs

  7. None
  8. None
  9. None
  10. None
  11. we have a problem

  12. None
  13. "This is so important, we can't entrust it to automation.

    We need our top developer to supervise it."
  14. None
  15. The Loose Parts Building blocks of better results

  16. automation everywhere

  17. None
  18. continuous integration

  19. None
  20. None
  21. None
  22. agile practices

  23. traceability

  24. rollback

  25. toggles

  26. None
  27. None
  28. humane interface

  29. None
  30. Divide and Conquer Small actions are generally best

  31. None
  32. None
  33. None
  34. None
  35. Automate Humans are creative. Robots are consistent.

  36. None
  37. None
  38. continuous integration servers

  39. continuous integration servers jenkins travis ci circleci buildhive

  40. None
  41. None
  42. None
  43. None
  44. None
  45. Embrace Transient-ness Hardware on demand provides flexibility

  46. Cloudbees

  47. None
  48. Amazon Web Services

  49. None
  50. Heroku

  51. None
  52. Hubot

  53. None
  54. hubot: <dosomething>

  55. Measure Identify mistakes at home and in the wild

  56. None
  57. None
  58. None
  59. None
  60. None
  61. None
  62. None
  63. None
  64. Feature Flags Dip toes, not heads, into unknown waters

  65. http://www.flickr.com/photos/mwichary/3209181446/

  66. None
  67. None
  68. Fail Forward Fix the root of problems

  69. None
  70. git revert

  71. None
  72. small changes

  73. try not to roll back

  74. fail forward

  75. Listen to Leaders Open sourcing all of the ideas

  76. None
  77. None
  78. None
  79. Risks What's the worst that could happen?

  80. kill some features

  81. discover we're wrong

  82. cause some regressions

  83. optimize for innovation

  84. Q&A

  85. matthew@github.com github.com/training @matthewmccull matthewmccullough