Downloaded 12 times
Uploaded byDavid Funaro
The Continuous delivery Value @ codemotion 2014
The document discusses the principles and practices of Continuous Delivery (CD) in software development, emphasizing the importance of low-risk, frequent, and predictable deployments to enhance application functionality. It outlines key requirements such as source code management, continuous integration, automated deployment, and the challenges faced during the release process. The author highlights the benefits of automation in reducing errors and stress, while encouraging best practices to ensure efficient communication and integration among team members.
More Related Content
Similar to The Continuous delivery Value @ codemotion 2014
![[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)
The Continuous delivery Value @ codemotion 2014
- 1. The Continuous DeliveryValue 12- 04 - 2014 ROME 11-12 April 2014 David Funaro Crash dei sistemi, Migrazioni fallite, aggiornamenti interrotti: sono tutte problematiche che nessuno vorrebbe mai incontrare durante l'introduzione di nuove funzionalità nel proprio applicativo (deploy) e ... la speranza non basta. L'attività di deploy è importante tanto quanto quelle che la precedono. La Continuous Delivery è un insieme di strumenti e metodologie che permetteranno di rendere i rilasci a basso rischio, economici, veloci, predicibili e ... sonni tranquilli. [email protected]
- 2. The Continuous Delivery Value 12 - 04 - 2014
- 3.
- 4.
- 5.
- 6. WRONG WAY This talkis for you…
- 7.
- 8. Facts keep system upand running release new features as soon as possible IT Business
- 9.
- 10. RELEASE FEEDBACK new features monetizebug performance layout
- 11. RELEASE ? Miss ReleasePrice ? €
- 12.
- 13. • How manytime you need to release software Time
- 14. • 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
- 15. • Have, theselected person, all the skill needed to terminate the procedure ? • What about his behavior in some exception flow case Skills
- 16. • How manypeople you need ? • For how many time ? • Other Resources ? Cost
- 17. • are youable to indicate how much time will care ? Predictable
- 18. • What aboutthe stress • stress => error-prone Stress
- 19. • Just finisha deploy. Software released.A bug is found.You have to re-start the deploy procedure Repeatability
- 20.
- 21.
- 22. Lots of thingsto consider • Code evolution • Code dependency management • System evolution management • Data management and architecture • Component management
- 23. Software Release • LowRisk • Cheap • Frequent • Rapid • Predictable ... should be Continuous Delivery
- 24. CD requirements • SourceCode Management • Continuous Integration Server • Automated Deploy • Real Time Alerting • Root Cause Analysis
- 25. CD FLOW Commit /push Automated Testing FAIL SUCCESSAutomated Deploy Procedure notify Basic Scenario
- 27. Deploy Pipeline Commit Stage Compile UnitTest Analysis BuildInstallers Release Automated acceptance testign Automated capacity testing Manual Testing Showcases Explorarory testing example
- 28.
- 29. Anti-patterns • Deploy softwaremanually • Manual Configuration • Deploy to a production-like Env Only after development is complete
- 30. Benefits • Empower Team •Reducing Errors • Lowering Stress • Deployment Flexibility • Practice Make Perfect
- 31. Keep Everything inversion control Automate Almost Everything Principles If it hurts, do i more frequently Done means released Build quality in
- 32. SECTION I Source CodeManagement
- 33. i sent youa mail with the last change ... are you shure ? i can’t find the new file ?!? The problem
- 35. SCM :What isit ? 3 5 7 10 Repository
- 36.
- 37.
- 38. SCM :What itdoes ? • Keeping multiple file version • Collaboration
- 39.
- 40.
- 41.
- 42. isn’t just forsource code Cautions you need everything required to re-create your application’s binaries and the environments in which they run.
- 43. Best Practice • LittleCommit • Frequent Commit • Consistent commit • User Meaningful Commit message
- 44.
- 45.
- 46. After your commit nothingworks anymore Ops INTEGRATION PROBLEM (after one commit ) After your commit nothing works anymore But ...“was working on my computer”
- 47. Ops(after deploy inprod) INTEGRATION PROBLEM It was working on the stage environment !!!
- 48. sleepless nights beforedemo ... bug just after release
- 49. Cost Analysis Design ImplementationTesting Release Resolve defects
- 50.
- 51. In software developmentthe components integration need to be tested continuosly... ! in order to find inconsistencies as soon as possible Good Solution
- 52.
- 53. 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
- 54.
- 55.
- 56.
- 57. F F F F F FF F Checkout last Commit CIFlow Build andTests Process
- 58. 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
- 59. 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
- 60. CI - Output SystemStatus Documentation/Artifacts Quality Check
- 61. “Continuous Integration doesn’tget rid of bugs, but it does make them dramatically easier to find and remove.” Martin Fowler
- 62. Ci - Bestpractice • CI server === Production Server • Integrate it from the first commit • Find best way to get notified
- 63. Immediate feedback onthe health of the system
- 65. Ci - software ...more and more
- 66.
- 67. Deployment “is all theactivities that make a software system available for use” Wikipedia
- 68. A Critical partof the application life-cycle Deployment
- 69.
- 70. Deployment • Low Risk •Cheap • Frequent • Rapid • Predictable
- 71. Low Risk • Exceptioncatched • Rollback • Data on secure
- 72. Cheap • no morethan one click • no more than one person • no skilled person
- 73. Frequent • to getfeedback
- 74.
- 75.
- 76.
- 77. is that adeploy procedure ? $ git pull origin master $ svn update Remote Desktop Versioning update
- 78. • Incomplete • Manualprocedure • Slow • Server Downtime • No data migration • No Rollback Problems
- 79.
- 80. one click deploy Deploy AutomatedDeployment Goals
- 81. AnyTime AnyWhere AnyOne AutomatedDeployment Goals
- 82.
- 83.
- 84. Scalable Frontend 1 Frontend1I Frontend III Balancer Automated Deployment Goals
- 85. Deployment Elements • ExecutableCode • Dependency Management • Software configuration • Infrastructure Management • Data Migrations • Manage Cache • Manage Assets
- 86.
- 87.
- 88. 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
- 89.
- 91.
- 92. What if, afteryour first production deployment, you have to change the Entity Relationship ?
- 94.
- 95. 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
- 96. A way tosetup your environment
- 97.
- 98.
- 99.
- 100. Manual - Followrecipe • Integrity problems • Problem with exception handling • Basic Skills requirements • Time consuming - expensive • Error - prone • Stress
- 101. Build a customScript • Do a backup • Create new directory • Update the code • Update dependencies • Run migration data • Update Environements • Warm up cache • ...
- 103. Existing Tools Fabric ... andmore others
- 104. Build quality in Donemeans released If it hurts, do i more frequently Automate Almost Everything Keep Everything in version control
- 106.