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

Continuous Delivery • A GitHub Story

Matthew McCullough
October 02, 2012
Programming
13
3.8k

Continuous Delivery • A GitHub Story

Matthew McCullough

October 02, 2012
Tweet

More Decks by Matthew McCullough

See All by Matthew McCullough
Patterns for Collaborative Software Development in a Social World at JavaOne 2015
matthewmccullough
1
370
Collaborative Software Development in a Social World at the Utah JUG
matthewmccullough
2
150
Git and GitHub Platform Review
matthewmccullough
1
410
Your First Pull Request
matthewmccullough
0
270
Git and GitHub Workflows at the Utah JUG
matthewmccullough
1
790
Agile-ish life at GitHub
matthewmccullough
2
350
Git and GitHub Agile Workflows for HP
matthewmccullough
0
280
Writing Tools on the GitHub Platform
matthewmccullough
0
240
Git Feature Branches as an Art
matthewmccullough
0
150

Other Decks in Programming

See All in Programming
AWS re:Invent 2024個人的まとめ
satoshi256kbyte
0
100
見えないメモリを観測する: PHP 8.4 `pg_result_memory_size()` とSQL結果のメモリ管理
kentaroutakeda
0
930
生成AIでGitHubソースコード取得して仕様書を作成
shukob
0
630
どうして手を動かすよりもチーム内のコードレビューを優先するべきなのか
okashoi
3
870
ErdMap: Thinking about a map for Rails applications
makicamel
1
630
PHPカンファレンス 2024｜共創を加速するための若手の技術挑戦
weddingpark
0
140
はてなにおけるfujiwara-wareの活用やecspressoのCI/CD構成 / Fujiwara Tech Conference 2025
cohalz
3
2.7k
技術的負債と向き合うカイゼン活動を1年続けて分かった "持続可能" なプロダクト開発
yuichiro_serita
0
300
ドメインイベント増えすぎ問題
h0r15h0
2
560
ecspresso, ecschedule, lambroll を PipeCDプラグインとして動かしてみた （プロトタイプ）　/ Running ecspresso, ecschedule, and lambroll as PipeCD Plugins (prototype)
tkikuc
2
1.8k
PHPで作るWebSocketサーバー ~リアクティブなアプリケーションを知るために~ / WebSocket Server in PHP - To know reactive applications
seike460
PRO
2
770
traP の部内 ISUCON とそれを支えるポータル / PISCON Portal
ikura_hamu
0
180

Featured

See All Featured
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
280
13k
Optimising Largest Contentful Paint
csswizardry
33
3k
GraphQLとの向き合い方2022年版
quramy
44
13k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
127
18k
Making Projects Easy
brettharned
116
6k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
33
2.7k
Building Flexible Design Systems
yeseniaperezcruz
328
38k
How to Think Like a Performance Engineer
csswizardry
22
1.3k
Designing on Purpose - Digital PM Summit 2013
jponch
116
7.1k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
160
15k
How STYLIGHT went responsive
nonsquared
96
5.3k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
10
870

Transcript

  1. How I learned to stop worrying and love the deploy

    CONTINUOUS D E L I V E R Y

  2. [email protected] github.com/training @matthewmccull matthewmccullough

  3. None
  4. None

  5. Why? The current state of affairs

  6. None
  7. None
  8. None
  9. None

  10. we have a problem

  11. None

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

    We need our top developer to supervise it."

  13. The Loose Parts Building blocks of better results

  14. automation everywhere

  15. continuous integration

  16. agile practices

  17. traceability

  18. rollback

  19. toggles

  20. humane interface

  21. Divide and Conquer Small actions are generally best

  22. None
  23. None
  24. None

  25. Automate Humans are creative. Robots are consistent.

  26. None
  27. None

  28. continuous integration servers

  29. continuous integration servers jenkins travis ci circleci buildhive

  30. None
  31. None
  32. None
  33. None
  34. None

  35. Embrace Transient-ness Hardware on demand provides flexibility

  36. Azure

  37. None

  38. AppHarbor

  39. None

  40. Cloudbees

  41. None

  42. Amazon Web Services

  43. None

  44. Heroku

  45. None

  46. Hubot

  47. None

  48. hubot: <dosomething>

  49. Measure Identify mistakes at home and in the wild

  50. None
  51. None
  52. None
  53. None
  54. None
  55. None
  56. None
  57. None

  58. Feature Flags Dip toes, not heads, into unknown waters

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

  60. None
  61. None

  62. Fail Forward Fix the root of problems

  63. git revert

  64. small changes

  65. try not to roll back

  66. fail forward

  67. Listen to Leaders Open sourcing all of the ideas

  68. None
  69. None
  70. None

  71. Risks What's the worst that could happen?

  72. kill some features

  73. discover we're wrong

  74. cause some regressions

  75. Q&A

  76. [email protected] github.com/training @matthewmccull matthewmccullough