Continous delivery

download Continous delivery

If you can't read please download the document

  • date post

    11-May-2015
  • Category

    Technology

  • view

    1.006
  • download

    0

Embed Size (px)

Transcript of Continous delivery

  • 1.Andrzej GrzesikMonday, July 2, 12

2. CONTINOUS DELIVERY jak to ugry?Andrzej GrzesikMonday, July 2, 12 3. GREAT BOOKS!Monday, July 2, 12 4. 3.6% prelegentw jest zMonday, July 2, 12 5. ABOUT:MEPresentPastMonday, July 2, 12 6. I HATE COMPUTERS disclaimerMonday, July 2, 12 7. QUESTIONS?ask them right away!Monday, July 2, 12 8. So...Monday, July 2, 12 9. because is more fun thanMonday, July 2, 12 10. what is.. done?Monday, July 2, 12 11. #dene doneMonday, July 2, 12 12. What is done?Monday, July 2, 12 13. What is done? CodedMonday, July 2, 12 14. What is done? Coded Checked-inMonday, July 2, 12 15. What is done? Coded Checked-in ReviewedMonday, July 2, 12 16. What is done? Coded Checked-in Reviewed BuiltMonday, July 2, 12 17. What is done? Coded Checked-in Reviewed Built TestedMonday, July 2, 12 18. What is done? Coded Checked-in Reviewed Built Tested DemoedMonday, July 2, 12 19. not really :-)Monday, July 2, 12 20. #redene doneMonday, July 2, 12 21. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.Monday, July 2, 12 22. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Agile ManifestoMonday, July 2, 12 23. its not ready till its deployed done === releasedMonday, July 2, 12 24. feedback!Monday, July 2, 12 25. Eric Ries, The Lean Startupbuild& create hypothesis ideas&deploy& deliver minimum viable product get feedback learn&measure& (repeat) data&Monday, July 2, 12 26. If we can reduce the time between major iterations We can increase our odds of successEric Ries, Lean StartupMonday, July 2, 12 27. If we can reduce the time between major iterations We can increase our odds of successEric Ries, Lean StartupMonday, July 2, 12 28. How long would it take your organization to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis?Mary and Tom Poppendieck,Implementing Lean Software DevelopmentMonday, July 2, 12 29. How long would it take your organization to deploy a change that involved just one single line of code? Do you do this on a repeatable, reliable basis?Mary and Tom Poppendieck,Implementing Lean Software DevelopmentMonday, July 2, 12 30. repeatableMonday, July 2, 12 31. HOW?!Monday, July 2, 12 32. entreth: The Deployment PipelineMonday, July 2, 12 33. The Deployment PipelineMonday, July 2, 12 34. The Deployment PipelinecompileMonday, July 2, 12 35. The Deployment Pipelinecompileunit testMonday, July 2, 12 36. The Deployment Pipelinecompileunit test packageMonday, July 2, 12 37. The Deployment Pipelinecompileunit test package artifact repositoryMonday, July 2, 12 38. The Deployment PipelinecompileAcceptanceunit testtesting packageartifact repositoryMonday, July 2, 12 39. The Deployment PipelinecompileAcceptance Capacityunit testtesting testing packageartifact repositoryMonday, July 2, 12 40. The Deployment PipelinecompileAcceptance Capacity Manualunit testtesting testing testing packageartifact repositoryMonday, July 2, 12 41. The Deployment PipelinecompileAcceptance Capacity Manualunit testtestingReleasetesting testing packageartifact repositoryMonday, July 2, 12 42. build only once!Monday, July 2, 12 43. The Deployment PipelineMonday, July 2, 12 44. The Deployment PipelinecompileAcceptance Capacityunit testtesting testing packageartifact repositoryMonday, July 2, 12 45. The Deployment PipelinecompileAcceptance Capacity Manualunit testtesting testing testing packageartifact repositoryMonday, July 2, 12 46. The Deployment PipelinecompileAcceptance Capacity Manualunit testtestingReleasetesting testing packageartifact repositoryMonday, July 2, 12 47. The Deploymentfear! PipelinecompileAcceptance Capacity Manualunit testtestingReleasetesting testing packageartifact repositoryMonday, July 2, 12 48. automate everything! (almost)Monday, July 2, 12 49. automate everything!Monday, July 2, 12 50. and?Monday, July 2, 12 51. well, its BIGMonday, July 2, 12 52. all code is production readyMonday, July 2, 12 53. every version is a Release CandidateMonday, July 2, 12 54. Pro tip: --versionMonday, July 2, 12 55. antipatternsMonday, July 2, 12 56. deploying manuallyis evil!Monday, July 2, 12 57. error-pronehttp://www.ickr.com/photos/aaronjacobs/64368770/Monday, July 2, 12 58. always differentrepeatableMonday, July 2, 12 59. impossible to testMonday, July 2, 12 60. voodoo http://ickr.com/photos/35541100@N00/2486381001/Monday, July 2, 12 61. 2 AM deploys http://www.ickr.com/photos/dhdesign/1096464615/sizes/z/in/photostream/Monday, July 2, 12 62. the deploy teamMonday, July 2, 12 63. deploying rarely/latesymptomps: alpha, beta, goldMonday, July 2, 12 64. Monday, July 2, 12 65. deploying rarely late rst contact with reality creates unrealistic assumptions tested.. in devMonday, July 2, 12 66. do you avoid deploys?Monday, July 2, 12 67. deploy each? year quarter week ...Monday, July 2, 12 68. if it hurts do it more often!practice, practice, practiceMonday, July 2, 12 69. incremental, frequentreleases reduce riskMonday, July 2, 12 70. provide dataMonday, July 2, 12 71. give rollback pointsMonday, July 2, 12 72. some stats Facebook - deploy every 10 minutes Netix Etsy - 50-60 deploys/day last project - 1374 commits, 1057 deployments,