Continuous delivery @wcap 5-09-2013
7 likes1,545 views
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.
Continuous delivery @wcap 5-09-2013
- 1. Continuous Delivery 05 - 09 - 2013
- 3. Overview
- 4. STARTUP
- 5. STARTUP
- 8. • is the only phase ? • it’s really sufficient to release software Implementation
- 16. SW - LC Feedback
- 17. SW - LC Feedback • New Features • Bug fixing • System specification Changes • Web services changes • Customer support tips
- 20. RELEASE FEEDBACK new features monetize bug performance layout
- 21. RELEASE ? Miss Release Price ? €
- 23. Reaction Metrics Change RELEASE Time interval ... Security Skills Cost Predictable Stress Repeatability
- 24. • How many time you need to release software Time interval ...
- 25. • Everything will be 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, the selected person, all the skill needed to terminate the procedure ? • What about his behavior in some exception flow case Skills
- 27. • How many people you need ? • For how many time ? • Other Resources ? Cost
- 28. • are able to indicate how much time will care ? Predictable
- 29. • What about the stress • stress => error-prone Stress
- 30. • Just finish a 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
- 35. Lots of things to consider • Code dependency management • System evolution management • Data management and architecture • Component management
- 36. Software Release • Low Risk • 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 Build Installers Release Automated acceptance testign Automated capacity testing Manual Testing Showcases Explorarory testing
- 39. Overview Commit /push Testing FAIL SUCCESS Automated Deploy Procedure dev team
- 41. Anti-patterns • Deploy software manually • 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 in version control Automate Almost Everything Keys
- 44. PAUSE
- 45. SECTION I Source Code Management
- 46. i sent you a mail with the last change ... are you shure ? i can’t find the new file ?!? The problem
- 49. SCM :What is it ? 3 5 7 10 Repository
- 50. SCM :What it does ? •Keeping multiple file version •Collaboration
- 51. CHECK POINT
- 53. Sharing
- 54. isn’t just for source code Cautions you need everything required to re-create your application’s binaries and the environments in which they run.
- 55. How it works
- 56. Trunk/Master
- 64. Tag
- 65. Best Practice • Little Commit • Frequent Commit • Consistent commit • User Meaningful Commit message
- 67. DEMO
- 68. PAUSE
- 70. After your commit nothing works anymore But ...“was working on my computer” Ops INTEGRATION PROBLEM (dopo un commit )
- 71. It was working on the stage environment !!! Ops(dopo un deploy in produzione) INTEGRATION PROBLEM
- 72. sleepless nights before demo ... bug just after release
- 73. Cost Analysis Design Implementation Testing Maintenance Changes
- 78. In software development the components integration need to be tested continuosly... in order to find inconsistencies as soon as possible Good Solution
- 80. Continuous Integration is a 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
- 82. Requirements
- 83. Test Scopes
- 85. CI Flow
- 86. F CI Flow
- 87. F Checkout last Commit CI Flow Build andTests Process
- 88. F Checkout last Commit CI Flow Build andTests Process
- 89. F F F Checkout last Commit CI Flow Build andTests Process
- 90. F F F F F F Checkout last Commit CI Flow Build andTests Process
- 91. F F F F F FF F Checkout last Commit CI Flow Build andTests Process
- 92. F F F F F FF F Checkout last Commit CI Flow Build andTests Process
- 94. Build & Test ✓Process creating 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 - Reduce Risk • 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 System Status Documentation/Artifacts Quality Check
- 97. “Continuous Integration doesn’t get rid of bugs, but it does make them dramatically easier to find and remove.” Martin Fowler
- 98. Immediate feedback on the health of the system
- 99. DEMO
- 100. Team Responsibilities • Check in 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 - Best practice • CI server === Production Server • Integrate it from the first commit • Find best way to get notified
- 104. Ci - software ... more and more
- 105. PAUSA
- 107. Deployment “is all the activities that make a software system available for use” Wikipedia
- 108. A Critical part of the application life-cycle Deployment
- 109. RELEASE Real ?
- 111. Deployment • Low Risk • Cheap • Frequent • Rapid • Predictable
- 112. Low Risk • Exception catched • Rollback • Data on secure
- 113. Cheap • no more than one click • no more than one person • no skilled person
- 114. Frequent • to get feedback
- 115. Rapid
- 116. Predictable
- 117. Incomplete ways
- 118. Ftp is a deploy procedure ?
- 119. Rsync Rsync is a deploy procedure ?
- 120. TeamViewer Teamviewer is a deploy procedure ?
- 121. SCM $ git pull origin master $ svn update Versioning checkout is a deploy procedure ?
- 122. • Incomplete • Manual procedure • Slow • Server Downtime • No data migration • No Rollback Problems
- 124. one click deploy Deploy Automated Deployment Goals
- 125. AnyTime AnyWhere AnyOne Automated Deployment Goals
- 127. no downtime Automated Deployment Goals
- 128. Scalable Frontend 1 Frontend 1I Frontend III Balancer Automated Deployment Goals
- 129. Deployment Elements • Executable Code • Dependency Management • Software configuration • Environment Management • Data Migrations • Manage Cache • Manage Assets
- 132. How you keep updated 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. PIP
- 135. Data Migration
- 136. What if, after your first production deployment, you have to change the Entity Relationship ?
- 139. How you keep updated 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 way to setup your environment
- 145. Manual - Follow recipe • Integrity problems • Problem with exception handling • Basic Skills requirements • Time consuming - expensive • Error - prone • Stress
- 146. Build a custom Script • Do a backup • Create new directory • Update the code • Update dependencies • Run migration data • Update Environements • Warm up cache • ...
- 148. Existing Tools Fabric ... and more others
- 150. • Built in Ruby • Easy setup • Event Task based, easy to hook into • Multiple server • Multistage extension • Multiple recipe for different environments
- 156. DEMO
- 157. Keep Everything in version control Automate Almost Everything
- 159. Thanks