1. CONTINUOUS DELIVERY / CONTINUOUS INTEGRATION

2. IDEAS -> SOLUTIONS Time

3. TIME IS MONEY

4. TYPICAL RELEASE

5. AGILE MANIFESTO

6. CONTINUOUS DELIVERY Keep software in production ready state One button deploy Build the pipeline

7. The process for releasing/deploying software MUST be repeatable and reliable Automate everything! If something difficult or painful, do it more often Keep everything in source control Done means “released” Build quality in! (Metrics) Everybody has responsibility for the release process Improve continuously 8 PRINCIPLES OF CONTINUOUS DELIVERY

8. CONTINUOUS INTEGRATION VCS Checkout Build Tests Remote Repository

9. CONTINUOUS INTEGRATION TOOLS

10. BUILD PIPELINE

11. CONTINUOUS DELIVERY DevVCS Build server Sto- rage QA Stage Prod. Bug tracking system Smoke tests Feedback

12. DASHBOARD

13. CONTINUOUS DELIVERY EXAMPLE StageProductionAuto Deploy Load Balancer QA Engineers Auto Tests

14. CLOUD IS COOL Ready for automation Pay as you go Infrastructure as a code

15. CONTINUOUS DELIVERY IN CLOUD Stage 1 QA Engineers Auto Tests Stage 2Stage 3 Demo

16. DEMO

17. 17 OUR CONTACTS SpecialEPM-CITConsulting@epam.com http://cloud.epam.com https://twitter.com/EPAM_Cloud http://epamcloud.blogspot.com/ https://www.yammer.com/epam.com/