Continuous Deployment

Transcript

1. Zf2 contributor Modules developer - MARTIN SHWALBE @mshwalbe Hounddog
2. CONTINUOUS DEPLOYMENT
3. AUTOMATION
4. REDUCE CODE INVENTORY
5. REDUCE TECHNICAL DEBT
6. SAFETY
7. CONFIDENCE
8. HAPPY CUSTOMERS
9. HAPPY DEVELOPERS
10. CONTINUOUS DEPLOYMENT LIFECYCLE
12. CONTINUOUS INTEGRATION "Continuous Integration is a software development practice where members of a team integrate their work frequently" -- Martin Fowler
13. ADVANTAGES Continously integrate new code with the existing code repository All tests run at each integration cycle Immidiate Feedback of code quality through Metrics Constant availability of a deployable source Increased Visibility
14. CONTINUOUS INTEGRATION Continuous Integration without tests does not work Start developing tests Write tests for each new identified bug Develop tests for each new feature
15. ZERO DOWNTIME DEPLOYMENT Symlink production directory nodejs: switch port or any other method you can come up with
16. UI UPGRADES Keep visible feature changes hidden until they are ready i f ( $ c o n f i g . f e a t u r e ) { / / S h o w s o m e c o o l n e w s t u f f } e l s e { / / S h o w o l d b o r i n g s t u f f }
17. OLD BORING UI
18. NEW COOL FEATURE
19. DATABASE UPGRADES Enable automatic upgrading of your database schema
20. DATABASE UPGRADE Synchronize Database and Code on deployment Apply Non Destructive Upgrades Make Schema changes Downgradable
21. ADDITIONS DO NOT CAUSE ANY PROBLEMS
22. WORKING ENVIRONMENT
23. DESTRUCTIVE DATABASE UPGRADE
24. UNHAPPY CUSTOMER
25. DESTRUCTIVE DATABASE UPGRADE Destructive changes need a bit more care, the degree of which depends on the degree of destruction involved
26. WORKING ENVIRONMENT
27. DATABASE UPGRADE Apply changes without breaking backwards compatibility
28. DATABASE UPGRADE Apply changes without breaking backwards compatibility
29. CI Platform CI Server CI & Release Management AVAILABLE TOOLS ONE-Click App Releases many more...
30. THANK YOU Questions? Martin Shwalbe | @mshwalbe