Continuous Delivery at GitHub

Continuous Delivery (CD) is the practice of building software that is ready to be deployed to production at all times. CD requires a stable, automated build pipeline, with simple, push button deployments, guided by feedback and metrics on the health of the production system. By refining and shortening feedback loops throughout the entire software process, it is possible to continually be delivering high-quality, working software to happy customers. At GitHub, we deploy hundreds of times in the course of an average day. We practice continuous delivery from design, development and ops, through our release processes and into customer support. This talk will cover many of the techniques and tools we use for continuous delivery at GitHub, including pull requests, feature toggles, chat ops and continuous integration and deployment. We will also discuss core principles so you can apply these lessons in your own team, process, and business.

Transcript

1. at GitHub Continuous Delivery ! !
2. How good are you at solving a problem?
9. It wasn’t always like this, you know…
14. How good are you at solving a problem?
15. First attempts at solving a problem
16. Slow
17. Error-prone
18. Decent chance of failure
19. But there’s no way you’re getting to
21. Without a little
23. The good news is
24. Your solution can get better over time.
25. Working solution Better Solution Good solution Great solution
29. “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” http://agilemanifesto.org/principles.html Principles behind the Agile Manifesto
30. ! ! We want to make it easier to work together than to work alone.
31. Share work earlier, and more often
42. Open a pull request to share your direction
43. Roll out pieces of a system incrementally
44. Build a demo of the feature Ship it to staff Get feedback Ship it to all users
47. Feature flags/toggles
48. class ApplicationController < ActionController::Base! ! def conversation_locking_enabled?! current_user && current_user.conversation_locking_enabled?! end! helper_method :conversation_locking_enabled?! ! end!
49. <% if logged_in? && && current_user.conversation_locking_enabled? && issue.repository.writable_by?(current_user) %>! <%! type = issue.pull_request? ? "pull request" : "issue"! verb = issue.locked? ? "unlock" : "lock"! next_state = (verb == "unlock" ? "lock" : "unlock")! %>! ! <div class="discussion-sidebar-item lock-toggle">! <a href="#lock-confirmation" rel="facebox" class="lock-toggle-link">! <% if verb == "lock" %>! <span class="octicon octicon-lock"></span>! <% else %>! <span class="octicon octicon-key"></span>! <% end %>! <%= verb.capitalize %> <%= type %>! </a>! </div>! <% end %>!
50. class User! module FeatureFlagMethods! ! def preview_features?! GitHub.preview_features_enabled? && staff?! end! ! # Issue locking! def conversation_locking_enabled?! preview_features?! end! ! end! end!
57. Build a demo of the feature Ship it to staff Get feedback Ship it to all users
61. Utilize feedback loops at each step
63. Tools that help you progress, and see progress ‣Version control ‣Automated test suite ‣Continuous integration ‣Group chat and ChatOps ‣Staging, QA, Production-like environments ‣Exception tracking ‣Metrics collection
64. Keep risk low and innovation high
65. Build a demo of the feature Ship it to staff Get feedback Ship it to all users
67. ! The End
68. ! @shayfrendt