Continuous deployment
- 2. How Long does it take to Deploy? More than a Year? Six months to a Year? One to six months? Two Weeks to a Month? One day to two Weeks? One hour to one day? One day to two Weeks? Less than 10 Minutes?
- 3. How Long does it take to Deploy?
- 4. Continuous Deployment is a repeatable methodology to deploying code
- 5. Continuous Deployment is Automation
- 6. Deployment Reduces Code Inventory
- 8. Continuous Deployment is Safety
- 9. Fast Turnaround leads to Happy Customers
- 10. … and happy developers
- 11. Traditional Release Cycle Timeline 1-4 Weeks Development Release Cut Stage QA Fix Bugs Integrate Release! Patches
- 12. Continuous Deployment Release Cycle Timeline 5-10 Minutes Automated QA Development x x Release Cut Stage x Testing and Fix Bugs Staging x Integrate Patches Deploy Release!
- 13. Tools Jenkins Statistic Analysers
- 16. Database Evolution in Continuous Deployment Updating Database is
- 19. Database Evolution: Addition Addtions do not cause any problems.
- 20. Destructive Database Evolution Destructive changes need a bit more care, the degree of which depends on the degree of destruction involved
- 23. Destructive Database Evolution Unhappy Customer!
- 24. Database Evolution Which comes first? Code or the Database?
- 25. Destructive Database Evolution Apply Changes without breaking backwards compatibility
- 26. Destructive Database Evolution The application can still read and write to the old columns
- 27. Destructive Database Evolution Update the application. //Keep this Request Select Address Data from Table User //Additional Request Select Address Data from Table Address
- 28. Destructive Database Evolution The application would read and write to both tables.
- 29. Destructive Database Evolution Cleanup the Application. SQL Script to copy old data from User table Select Address Data to Address table from Table Address
- 30. Destructive Database Evolution Delete the obsolete Columns
- 31. Thank you!