Download as PDF, PPTX
Uploaded byDavid Funaro
Continuous delivery @wcap 5-09-2013
The document discusses the principles and practices of continuous delivery in software development, emphasizing the importance of source code management, continuous integration, and automated deployment to ensure low-risk, rapid, and predictable software releases. It highlights various strategies, tools, and methodologies to improve the efficiency of the software delivery process while minimizing errors and stress on development teams. Key practices include thorough testing, version control, and effective handling of dependencies and configurations.
More Related Content
Similar to Continuous delivery @wcap 5-09-2013
![[2007] Tesi: Confronto tra riconoscitori vocali embedded e distribuiti per te...](https://cdn.slidesharecdn.com/ss_thumbnails/presentazionetesi-130217120452-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Continuous delivery @wcap 5-09-2013
- 1. Continuous Delivery 05 -09 - 2013
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8. • is theonly phase ? • it’s really sufficient to release software Implementation
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17. SW - LC Feedback •New Features • Bug fixing • System specification Changes • Web services changes • Customer support tips
- 18.
- 19.
- 20. RELEASE FEEDBACK new features monetizebug performance layout
- 21. RELEASE ? Miss ReleasePrice ? €
- 22.
- 23. Reaction Metrics Change RELEASE Time interval... Security Skills Cost Predictable Stress Repeatability
- 24. • How manytime you need to release software Time interval ...
- 25. • Everything willbe ok ? • Can i be sure that every needed step will be done ? • Exceptions, are managed ? • Data migration goes well ? • Can i go back (rollback) ? Security
- 26. • Have, theselected person, all the skill needed to terminate the procedure ? • What about his behavior in some exception flow case Skills
- 27. • How manypeople you need ? • For how many time ? • Other Resources ? Cost
- 28. • are ableto indicate how much time will care ? Predictable
- 29. • What aboutthe stress • stress => error-prone Stress
- 30. • Just finisha deploy. Software released.A bug is found.You have to re-start Repeatability
- 31. Reaction Metrics RELEASE Time interval... Security Skills Cost Predictable Stress Repeatability Production
- 32. Reaction Metrics RELEASE Time interval... Security Skills Cost Predictable Stress Repeatability Production Staging
- 33. Reaction Metrics RELEASE Time interval... Security Skills Cost Predictable Stress Repeatability Production Testing Staging
- 34.
- 35. Lots of thingsto consider • Code dependency management • System evolution management • Data management and architecture • Component management
- 36. Software Release • LowRisk • Cheap • Frequent • Rapid • Predictable ... should be Continuous Delivery
- 37. What we need •Source Code Management • Continuous Integration Server • Automated Deploy • Real Time Alerting • Root Cause Analysis
- 38. Deploy Pipeline Commit Stage Compile UnitTest Analysis BuildInstallers Release Automated acceptance testign Automated capacity testing Manual Testing Showcases Explorarory testing
- 39. Overview Commit /push Testing FAIL SUCCESSAutomated Deploy Procedure dev team
- 40.
- 41. Anti-patterns • Deploy softwaremanually • Manual Configuration • Deploy to a production-like Env Only after development is complete
- 42. Benefits • Empower Team •Reducing Errors • Lowering Stress • Deployment Flexibility • Practice Make Perfect
- 43. Keep Everything inversion control Automate Almost Everything Keys
- 44.
- 45. SECTION I Source CodeManagement
- 46. i sent youa mail with the last change ... are you shure ? i can’t find the new file ?!? The problem
- 49. SCM :What isit ? 3 5 7 10 Repository
- 50. SCM :What itdoes ? •Keeping multiple file version •Collaboration
- 51.
- 52.
- 53.
- 54. isn’t just forsource code Cautions you need everything required to re-create your application’s binaries and the environments in which they run.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65. Best Practice • LittleCommit • Frequent Commit • Consistent commit • User Meaningful Commit message
- 66.
- 67.
- 68.
- 69.
- 70. After your commit nothingworks anymore But ...“was working on my computer” Ops INTEGRATION PROBLEM (dopo un commit )
- 71. It was workingon the stage environment !!! Ops(dopo un deploy in produzione) INTEGRATION PROBLEM
- 72. sleepless nights beforedemo ... bug just after release
- 73. Cost Analysis Design ImplementationTesting Maintenance Changes
- 74.
- 75.
- 76.
- 77.
- 78. In software developmentthe components integration need to be tested continuosly... in order to find inconsistencies as soon as possible Good Solution
- 79.
- 80. Continuous Integration isa software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Martin Fowler
- 81.
- 82.
- 83.
- 84.
- 85.
- 86.
- 87. F Checkout last Commit CIFlow Build andTests Process
- 88. F Checkout last Commit CIFlow Build andTests Process
- 89. F F F Checkout last Commit CIFlow Build andTests Process
- 90. F F F F F F Checkout last Commit CIFlow Build andTests Process
- 91. F F F F F FF F Checkout last Commit CIFlow Build andTests Process
- 92. F F F F F FF F Checkout last Commit CIFlow Build andTests Process
- 93.
- 94. Build & Test ✓Processcreating executable code ✓Unit test ✓Quality criteria ✓FunctionalTest ✓Non FunctionalTest Valid Syntax Compile Code behavior Code coverage, Mass detector Business Acceptance Criteria Application performance PASS
- 95. CI - ReduceRisk • Say goodbye to long and tense integrations • Increase visibility which enables greater communication • Catch issues fast and nip them in the bud • Spend less time debugging and more time adding features • Proceed in the confidence you’re building on a solid foundation • Stop waiting to find out if your code’s going to work • Reduce integration problems allowing you to deliver software more rapidly
- 96. CI - Output SystemStatus Documentation/Artifacts Quality Check
- 97. “Continuous Integration doesn’tget rid of bugs, but it does make them dramatically easier to find and remove.” Martin Fowler
- 98. Immediate feedback onthe health of the system
- 99.
- 100. Team Responsibilities • Checkin frequently • Don’t check in broken code • Don’t check in untested code • Don’t check in when the build is broken • Repair the build as soon as possible
- 101. Ci - Bestpractice • CI server === Production Server • Integrate it from the first commit • Find best way to get notified
- 104. Ci - software ...more and more
- 105.
- 106.
- 107. Deployment “is all theactivities that make a software system available for use” Wikipedia
- 108. A Critical partof the application life-cycle Deployment
- 109.
- 110.
- 111. Deployment • Low Risk •Cheap • Frequent • Rapid • Predictable
- 112. Low Risk • Exceptioncatched • Rollback • Data on secure
- 113. Cheap • no morethan one click • no more than one person • no skilled person
- 114. Frequent • to getfeedback
- 115.
- 116.
- 117.
- 118. Ftp is adeploy procedure ?
- 119. Rsync Rsync is adeploy procedure ?
- 120. TeamViewer Teamviewer is adeploy procedure ?
- 121. SCM $ git pullorigin master $ svn update Versioning checkout is a deploy procedure ?
- 122. • Incomplete • Manualprocedure • Slow • Server Downtime • No data migration • No Rollback Problems
- 123.
- 124. one click deploy Deploy AutomatedDeployment Goals
- 125. AnyTime AnyWhere AnyOne AutomatedDeployment Goals
- 126.
- 127.
- 128. Scalable Frontend 1 Frontend1I Frontend III Balancer Automated Deployment Goals
- 129. Deployment Elements • ExecutableCode • Dependency Management • Software configuration • Environment Management • Data Migrations • Manage Cache • Manage Assets
- 130.
- 131.
- 132. How you keepupdated your libraries dependencies ? to get the feature 103 done, i use library XXX ok, i’ll note it here ... to get the feature 103 done, i use library XXX OK ..
- 133.
- 135.
- 136. What if, afteryour first production deployment, you have to change the Entity Relationship ?
- 138.
- 139. How you keepupdated your OS componets/ libraries ? to get the feature 103 done, i use library XXX, that require the module 288 ok, i’ll note it here ... to get the feature 103 done, i use library XXX, that require the module 903 OK ..
- 140. A new wayto setup your environment
- 141.
- 142.
- 143.
- 144.
- 145. Manual - Followrecipe • Integrity problems • Problem with exception handling • Basic Skills requirements • Time consuming - expensive • Error - prone • Stress
- 146. Build a customScript • Do a backup • Create new directory • Update the code • Update dependencies • Run migration data • Update Environements • Warm up cache • ...
- 148. Existing Tools Fabric ... andmore others
- 150. • Built inRuby • Easy setup • Event Task based, easy to hook into • Multiple server • Multistage extension • Multiple recipe for different environments
- 152.
- 153.
- 154.
- 155.
- 156.
- 157. Keep Everything inversion control Automate Almost Everything
- 159.