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

Iterate and Ship

181de1fb11dffe39774f3e2e23cda3b6?s=47 Armin Ronacher
May 10, 2016
Programming
4
330

Iterate and Ship

How we iterate and ship at Sentry.

181de1fb11dffe39774f3e2e23cda3b6?s=128

Armin Ronacher

May 10, 2016
Tweet

More Decks by Armin Ronacher

See All by Armin Ronacher
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
0
350
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
1
350
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
0
2k
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
5
730
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
19
8.4k
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
4
830
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
2
1.3k
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
4
580
181de1fb11dffe39774f3e2e23cda3b6?s=48 mitsuhiko
9
1.2k

Other Decks in Programming

See All in Programming
Ae7cc81ee2744719c66282681a219110?s=48 lnicolet
0
190
3cfad86677c5966ecfe9b81955fa3489?s=48 inoue2002
0
260
7437b838338581b08ca72340b05475b9?s=48 abt
0
120
0f50b010cc99988fba8a73008b21f353?s=48 e10dokup
0
770
Ba655e3712aaabfbca289fe136f85fe4?s=48 qnighy
0
230
6c6b60f0440e030040a9141cab781ed0?s=48 hiboma
0
290
62a14b322f22ab9588702ab2064df63f?s=48 shanpu
0
220
Ef1341e83c896b7b1c5061674951aa2c?s=48 kumashun
0
150
1eecfce54b4f902784d046328935efd4?s=48 makoto_inoue
0
400
Ad449f3f4e595ade283a30c4f66010be?s=48 seto_hi
1
4.3k
5afbf65e9e32cef9ab74e5b5347a5bce?s=48 korosuke613
0
300
6e704ad00f166b420eba3d174713c82b?s=48 urushiyama
0
410

Featured

See All Featured
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
449
36k
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
17
1.2k
5f83ef806155b403c3393160ce51f955?s=48 jlugia
218
16k
433acaea1012b25d97ae66da9b998dad?s=48 malarkey
122
16k
8ec1383b240b5ba15ffb9743fceb3c0e?s=48 philnash
22
1.1k
E9221b172e78e888355fa2fe4541b595?s=48 mclloyd
PRO
6
7.6k
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
372
43k
91cefdf141106fa10674aae74ce05890?s=48 yeseniaperezcruz
307
32k
95d9f37115fbb0d13135d0f77132f856?s=48 morganepeng
32
1.9k
C157b16234f1e75e8eac3698c1d4414a?s=48 ddemaree
272
32k
D67fff74178013024d833b3eec6cf27f?s=48 lynnandtonic
277
17k
A60068bce2e73de3a37ca9d2dbe36092?s=48 bryan
35
3.9k

Transcript

  1. Armin Ronacher iterate and ship

  2. Armin Ronacher @mitsuhiko Flask / Sentry / Lektor

  3. ̿ SENTRY ̀

  4. None
  5. None
  6. None

  7. ̿ THE TWO PRODUCTS ̀

  8. sentry vs ‘getsentry’

  9. sentry open source repo on-premise monthly releases

  10. ‘getsentry’ billing & quotas depends on sentry hourly deploys

  11. ̿ THE GOALS ̀

  12. deploy in seconds be unable to screw up and if

    you do: instant rollbacks

  13. tag a release once a month

  14. ̿ WORKFLOW ̀

  15. commit review integration deploy

  16. requires good test coverage requires good local setup makes it

    easier for newcomers

  17. ̿ COMMITTING ̀

  18. lint on commit!

  19. 1 Release / Month 5 Deployments / Day On Prem:

    Hosted:
  20. None

  21. master is stable

  22. 1. branch off master 2. pull request 3. merge

  23. all the pull requests

  24. !! AVOID DOWNTIME !!

  25. postgres <3 transactional ddl, concurrent indexes, cheap alter table add

    nullable columns

  26. bidirectional compatibility

  27. separation of state and connections

  28. ̿ CONTINUOUS TESTING ̀

  29. sentry travis-ci.org test all the code

  30. ‘getsentry’ travis-ci.com test code relevant for us

  31. ̿ CONTINUOUS DELIVERY ̀

  32. FREIGHT wait for travis > build > ship

  33. bidirectional communication with the main slack channel

  34. dev never matches prod :(

  35. thus: fast rollbacks! (backwards + forwards compatibility)

  36. ̿ CODE STRUCTURE ̀

  37. large systems are organisms

  38. not all things will run the same code at the

    same time

  39. data schema ~ code behavior

  40. break up larger features

  41. feature flag it! (we shipped some code to on-prem we

    backed out)

  42. ̿ MOVING PARTS ̀

  43. keep dev basic: fewer parts

  44. do not diverge dev from prod too much

  45. virtual machines and docker are not an acceptable dev environment

  46. ̿ REPRODUCIBLE BUILDS ̀

  47. pip freeze / npm shrinkwrap

  48. nothing is more frustrating than a failed deploy because a

    dependency of a dependency of a dependency of a dependency pushed out a broken release

  49. build once > ship to many

  50. ̿ MONITOR FAILURES ̀

  51. associate failures to users

  52. map support requests to failures

  53. use sentry :-)

  54. ̿ FRIENDLY ROBOTS ̀

  55. replace yourself!

  56. bots and webhooks

  57. github hooks

  58. notify to communication hub

  59. ̿ BETTER CLIMATE ̀

  60. the more robots, the better the integration, the smaller the

    fear of doing damage

  61. If you can launch a feature on your first day

    of work that's motivating

  62. also: happy customers

  63. Q&A