Continuous Delivery – A GitHub Story

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

Transcript

1. a GitHub Story CONTINUOUS D E L I V E R Y
2. matthew@github.com github.com/training @matthewmccull matthewmccullough
5. Probably the most important technical book of 2010 -Martin Fowler, ThoughtWorks
6. Why? The current state of affairs
11. we have a problem
13. "This is so important, we can't entrust it to automation. We need our top developer to supervise it."
15. The Loose Parts Building blocks of better results
16. automation everywhere
18. continuous integration
22. agile practices
23. traceability
24. rollback
25. toggles
28. humane interface
30. Divide and Conquer Small actions are generally best
35. Automate Humans are creative. Robots are consistent.
38. continuous integration servers
39. continuous integration servers jenkins travis ci circleci buildhive
45. Embrace Transient-ness Hardware on demand provides flexibility
46. Cloudbees
48. Amazon Web Services
50. Heroku
52. Hubot
54. hubot: <dosomething>
55. Measure Identify mistakes at home and in the wild
64. Feature Flags Dip toes, not heads, into unknown waters
65. http://www.flickr.com/photos/mwichary/3209181446/
68. Fail Forward Fix the root of problems
70. git revert
72. small changes
73. try not to roll back
74. fail forward
75. Listen to Leaders Open sourcing all of the ideas
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