Fast Deployment and Monitoring

Given at www.developermarch.com/developersummit/ 2014

Transcript

1. Fast Deployment and Monitoring Why continuous integration and ChatOps are crucial to every application Brent Beer GitHub Trainer @brntbeer
2. Fast Deployment and Monitoring Why continuous integration and ChatOps are crucial to every application
3. Agenda Who am I? Testing Hooks / Services ChapOps
4. Who am I?
5. Trainer
6. Developer
7. From the midwest
8. From the midwest of the US
11. In San Francisco now
13. Who even writes tests?
14. Who even writes tests first ?
15. I never did while in school
16. I still don't
17. I still don't
18. I'm geing beer!
19. Tests
20. "They take too long to write!"
21. "They take too long to write!" "I don't know how to write them"
22. "They take too long to write!" "I don't know how to write them" "My code is perfect"
23. "They take too long to write!" "I don't know how to write them" "My code is perfect" Lies! Lies! Lies!
24. Make it easy to write tests
25. script/cibuild
28. Sometimes running tests takes too long
29. Sometimes running tests takes too long
30. Not just for your Enterprise Applications
31. "Well older things still pass tests"
32. Share burden and responsibility
33. Never work alone
34. Never work alone
35. Pull Requests
36. Send yourself Pull Requests
37. Get others to do the work for you!
38. @mentions
39. @mentions
40. What if others could see if your tests were passing without running the code?
41. Hooks and Services
42. Make tests run easily for services
43. script/cibuild
44. Many third party services can be hooked into GitHub
45. Status API
46. Now someone visiting the Pull Request can know what's going on
47. Status Types
48. History of timeline statuses
49. Details
51. So many CI services
55. Self Configuration
57. Manual Configuration
60. Services can do more than just send data to the API
61. ChatOps
62. Context of the current state of things
63. Why Chat?
64. Hubot
65. Hubot
66. hubot.github.com
75. Hubot's Domain
76. Who does the things? Service? Hook? Robot?
77. Hubot: deploy all the things
78. Make it fast
79. Hubot: Make it fast
80. Deploys
82. "Hello @user, your deploy was successful, keep an eye on Haystack"
83. "Hello @user, your deploy was successful, keep an eye on Haystack"
85. Digging Deeper
86. Going beyond an exception
87. Graphite
88. Graphite
89. statsd and collectd
90. Now we have things reporting
91. Now we have things reporting
92. Who should fetch these graphs?
93. Maybe just a dashboard view?
94. Dashing
96. Dashboards
98. Group understanding
99. Group understanding
100. Useful commands
101. Hubot: help pager
102. Hubot: graph me -12h @network.border.cp1.bgp
103. Hubot: graph me -4h @browser.frontend
104. Hubot: deploy training- app/chronological to production
105. Teach by doing
106. This was always my main motivation with Hubot - teaching by doing by making this visible. It's an extremely powerful teaching technique. - @rtomayko
107. Signal vs Noise
108. Next Steps
109. Take a deep breath
110. Easy to run tests
111. More tests get wrien
112. Or collaborate
113. What's the state of the Pull Request?
114. What has been happening on the Pull Request
115. Your chatroom could be your office
116. Use robots
117. Use robots more
118. How do things look?
119. Don't bother me
120. Keep Deploying. Keep Building. Do it Faster & Safer.
121. Thank you! Brent Beer GitHub Trainer @brntbeer
122. References: hps://hubot.github.com hps://github.com/shopify/dashing hps://github.com/graphite-project hps://github.com/etsy/statsd/ hps://developer.github.com/v3/ hps://github.com/collectd hps://developer.github.com/v3/ hps://circleci.com/ hps://travis-ci.org/ hps://github.com/github/janky