Downloaded 13 times
Uploaded byJohannes Nicolai
How Github uses Github to develop and deploy GitHub
The document outlines how GitHub efficiently builds and ships software through continuous delivery and GitHub Flow, emphasizing asynchronous communication and collaboration via chatops. Key principles include responsive development, deployment confidence, and feature toggles to manage risk. It highlights GitHub's success with 18 million users and 37 million projects, and provides references for further understanding of the practices discussed.
More Related Content
Similar to How Github uses Github to develop and deploy GitHub
How Github uses Github to develop and deploy GitHub
- 1. the best wayto build and ship software How GitHub uses GitHub to develop and deploy GitHub Johannes Nicolai a @jonico - ! jonico@github.com @
- 2. "http://www.wired.com/2012/02/github-2/ Photo :Ariel Zambelich/Wired
- 3.
- 4. How software isbuilt GitHub Facts 4 " FOUNDED 2008 USERS 18M+ PROJECTS 37M MONTHLY VISITORS 40M CORPORATE CUSTOMERS 67k+ UNIVERSITIES 1000+ GLOBAL RANK 51 FORTUNE100 53% OFFICES San Francisco Tokyo, Amsterdam, Boulder
- 5. How software isbuilt 5 #GitHub Enterprise - Run your own GitHub behind your FW
- 6.
- 7. How software isbuilt 7 # OPEN SOURCE LEADERS SOFTWARE SPECIALISTS FORWARD THINKING ENTERPRISES How the world builds software
- 8. the best wayto build and ship software 8 " CONTINUOUS DELIVERY The (very shorten) recipe $ ASYNCHRONOUS COMMUNICATION% COMMON PHILOSOPHY& CHATOPS'
- 9. the best wayto build and ship software The Zen of GitHub 9 " • Responsive is better than fast • It’s not fully shipped until it’s fast • Anything added dilutes everything else • Practicality beats purity • Approachable is better than simple • Mind your words, they are important • Speak like a human • Half measures are as bad as nothing at all • Encourage flow • Non-blocking is better than blocking • Favor focus over features • Avoid administrative distraction • Design for failure • Keep it logically awesome
- 10. the best wayto build and ship software 10 " CONTINUOUS DELIVERY The (very shorten) recipe $ ASYNCHRONOUS COMMUNICATION% COMMON PHILOSOPHY& CHATOPS'
- 11. the best wayto build and ship software
- 12.
- 13. Create a FeatureBranch
- 14.
- 15. Open a PullRequest
- 16.
- 17. the best wayto build and ship software Get CI status back in Pull Request 17 "
- 18. the best wayto build and ship software Peer code reviews in Pull Request 18 "
- 19.
- 20.
- 21.
- 22. the best wayto build and ship software Deployment API 22 "
- 23. the best wayto build and ship software 23 " CONTINUOUS DELIVERY The (very shorten) recipe $ ASYNCHRONOUS COMMUNICATION% COMMON PHILOSOPHY& CHATOPS'
- 24.
- 25. the best wayto build and ship software Hubot 25 "
- 26. the best wayto build and ship software Hubot 26 "
- 27. the best wayto build and ship software What do you mean, “devops”? 27 "
- 28. the best wayto build and ship software What do you mean, “devops”? 28 " HTTP://WWW.EWEEK.COM/ENTERPRISE-APPS/SLIDESHOWS/DEVOPS-5-SIGNS-ENTERPRISES-NEED-TO-UNITE-THE-DEV-AND-OPS-CAMPS.HTML
- 29. the way peoplebuild software 29 'CHATOPS AS THE CULTURAL GLUE {) { * '+ DevOps APPLICATION AUTOMATION INFRASTRUCTURE AUTOMATION
- 30. the best wayto build and ship software
- 31. the best wayto build and ship software 31 " CONTINUOUS DELIVERY The (very shorten) recipe $ ASYNCHRONOUS COMMUNICATION% COMMON PHILOSOPHY& CHATOPS'
- 32. the best wayto build and ship software Deployments to production 32 "
- 33. the best wayto build and ship software Where Can I Deploy? 33 "
- 34. the best wayto build and ship software Deploy to test 34 "
- 35. the best wayto build and ship software Get deployment status back in PR 35 "
- 36. the best wayto build and ship software Deploy to production 36 "
- 37. the best wayto build and ship software Deploy to production - canary 37 "
- 38. the best wayto build and ship software Deploy to production - canary 38 "
- 39. the best wayto build and ship software Deploy to production - everywhere 39 "
- 40. the best wayto build and ship software Deployment confidence 40 "
- 41. the best wayto build and ship software Haystack 41 "
- 42. the best wayto build and ship software Hubot has your back 42 "
- 43. the best wayto build and ship software Hubot has your back 43 "
- 44.
- 45. the best wayto build and ship software Wrap it up 45 "
- 46. the best wayto build and ship software 46 " CONTINUOUS DELIVERY The (very shorten) recipe $ ASYNCHRONOUS COMMUNICATION% COMMON PHILOSOPHY& CHATOPS'
- 47.
- 48. the best wayto build and ship software Isn’t that still too risky??? 48 "
- 49. the best wayto build and ship software Feature Toggles 49 "
- 50. the best wayto build and ship software Feature Toggles 50 "
- 51. the best wayto build and ship software Feature Toggles 51 "
- 52. the best wayto build and ship software Science 52 "
- 53. the best wayto build and ship software Science 53 "
- 54. the best wayto build and ship software Science 54 "
- 55. the best wayto build and ship software Science 55 "
- 56. the best wayto build and ship software 'Hubot deployed on Heroku 56
- 57. the best wayto build and ship software 'Hubot deployed on Heroku 57
- 58. the best wayto build and ship software 58 "
- 59. the best wayto build and ship software 59 "
- 60. the best wayto build and ship software 60 "
- 61. the best wayto build and ship software References used within the presentation 61 " • https://github.com/blog/2093-how-the-services-team-uses-github • https://github.com/blog/1124-how-we-use-pull-requests-to-build-github • https://github.com/blog/1939-how-github-uses-github-to-document-github • https://www.youtube.com/watch?v=YIpNpptGX6Q • https://guides.github.com/introduction/flow/ • https://developer.github.com/v3/repos/deployments/ • http://githubengineering.com/deploying-branches-to-github-com/ • https://www.youtube.com/watch?v=NST3u-GjjFw • http://githubengineering.com/scientist/ • http://johnnunemaker.com/flipper/ • https://enterprise.github.com • https://paypal.github.io/InnerSourceCommons/ • https://github.com/blog/2079-managing-large-files-with-git-lfs
- 62.
- 63. the best wayto build and ship software Repo activity in the chat room 63 "
- 64. the best wayto build and ship software
- 65. the best wayto build and ship software Hubot 65 "
- 66. the best wayto build and ship software Hubot 66 "
- 67. the best wayto build and ship software Resources 67 "
- 69. the best wayto build and ship software Git 69 " • Started by Linus Torvalds 2005 (search “torvalds git” on youtube) • Easy branching and merging - content oriented, remembers origin • Small and fast - local operations, smaller repos • Distributed - VCS on my laptop, full copy incl. history • Data assurance - sha1, gpg • Staging area - crafted, meaningful commits • Free and open source - did you read the first line of this slide?
- 70. the best wayto build and ship software An ideal patch flow 70 " “(0) YOU COME UP WITH AN ITCH. YOU CODE IT UP. (1) SEND IT TO THE LIST AND CC PEOPLE WHO MAY NEED TO KNOW ABOUT THE CHANGE. (2) YOU GET COMMENTS AND SUGGESTIONS FOR IMPROVEMENTS. YOU MAY EVEN GET THEM IN A "ON TOP OF YOUR CHANGE" PATCH FORM. (3) POLISH, REFINE, AND RE-SEND TO THE LIST AND THE PEOPLE WHO SPEND THEIR TIME TO IMPROVE YOUR PATCH. GO BACK TO STEP (2). (4) THE LIST FORMS CONSENSUS THAT THE LAST ROUND OF YOUR PATCH IS GOOD. SEND IT TO THE MAINTAINER AND CC THE LIST. (5) A TOPIC BRANCH IS CREATED WITH THE PATCH AND IS MERGED TO ‘NEXT', AND COOKED FURTHER AND EVENTUALLY GRADUATES TO ‘MASTER'. - HTTPS://GITHUB.COM/GIT/GIT/BLOB/MASTER/DOCUMENTATION/SUBMITTINGPATCHES
- 71. the best wayto build and ship software Hubot has your back 71 "
- 72. the best wayto build and ship software Hubot has your back 72 "
- 73. the best wayto build and ship software Continuous Integration 73 "
- 74. the best wayto build and ship software Wrap it up 74 "