Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Enabling Continuous Delivery

423 vues

Publié le

The primary goals of this presentation are to:

- Give a brief, platform-agnostic overview of the 'why' and 'what' of Continuous Delivery. The purpose is to simply educate the student and bring everyone to the same level.
- Explain how Cloud Foundry benefits Continuous Delivery.
- Provide a hands-on lab experience where the student takes a - Spring Boot microservice application and builds a continuous delivery pipeline for it using Jenkins, Artifactory and Cloud Foundry. This is all done using free trial SaaS versions of the software.

Publié dans : Technologie
  • Soyez le premier à commenter

Enabling Continuous Delivery

  1. 1. © Copyright 2014 Pivotal. All rights reserved. Pivotal Cloud Platform Deep Dive Enabling Continuous Delivery Luke Shannon lshannon@pivotal.io 1
  2. 2. 2
  3. 3. Make Releases Boring 3
  4. 4. Continuous Delivery 4 Produce software in short cycles and ensure it can be reliably released at any time
  5. 5. Continuous Delivery != Continuous Deployment 5
  6. 6. The Difference: Who Presses The Button For A Production Deployment? 6
  7. 7. What happens without CD? 7
  8. 8. Long Cycle Time www.flickr.com/photos/nnova/33999049538 How Long Does It Take To Deploy One Line Of Code To Production?
  9. 9. No Feedback Loop www.flickr.com/photos/tenspeedphotography/54504567839 Water-scrum-fall?
  10. 10. Snowflake Environments 10 Your tests are invalid
  11. 11. 11 Fear of Change Production Breaks When Changes Are Made (!) … Right?
  12. 12. Process Gridlock www.flickr.com/photos/kevgilmour/484305133112 You Need To Open A Ticket For That!
  13. 13. 13
  14. 14. Strategies For Success 14
  15. 15. Strategies For Success Do Implement Continuous Integration 15
  16. 16. Strategies For Success Do Not Create Environment Specific Packages 16
  17. 17. DEV QA PROD
  18. 18. Strategies For Success Do Externalize Environment Specific Configuration 18
  19. 19. Strategies For Success Do Automate Everything 19
  20. 20. Strategies For Success Do Not Assume Existing Processes Are Right (Engage In Continuous Improvement) 20
  21. 21. Strategies For Success Do Not Use A Different Process For Different Environments 21
  22. 22. Strategies For Success Do Recreate App Environments Frequently (Also Known As: Servers Are Not Puppies) 22
  23. 23. X
  24. 24. Strategies For Success Do Deploy Less, More Frequently 24
  25. 25. Strategies For Success Do Automate All Testing Where Test Failures Would Prevent A Production Release From Occurring 25
  26. 26. How Cloud Foundry Helps 26
  27. 27. Cloud Foundry Helps… Get A New App Environment In Seconds 27 in a
  28. 28. Cloud Foundry Helps… Have Complete Consistency Between Environments 28
  29. 29. Cloud Foundry Helps… Have A Consistent API To Automate Deployments 29
  30. 30. Cloud Foundry Helps… Inject Environment Specific Configuration 30
  31. 31. 31 Promote Apps Through Environments With The Same Process Cloud Foundry Helps…
  32. 32. Cloud Foundry Helps… By Providing New Options: + Canary Deployment + Zero Downtime Deployment + A/B Testing + Scale Apps On-Demand + Autoscaling Apps 32
  33. 33. App Developers Can Be More Successful When They Are Supported By Agile Infrastructure 33
  34. 34. Example 34

×