Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

DevOps Practices: Continuous Delivery


Published on

The DevOps movement, like its Agile predecessor, is focused on improving the communication and collaboration between the development and operations teams responsible for different aspects of an app throughout its lifecycle. While successful DevOps initiatives start and end with organizational and cultural change, there are also common practices that are enablers and/or tools used in support of DevOps. In this session you will learn about the DevOps practice of Continuous Delivery—releasing and deploying application changes as they are available, and not waiting for big, cumbersome roll-ups of new code. This session will focus on the practice of Continuous Delivery, while demonstrating a few tools that can make implementing Continuous Delivery easier, including tools for automated provisioning and release orchestration. If you are interested in implementing a DevOps initiative in your organization, then this session is a must-see.

Published in: Technology, Design
  • ⇒⇒⇒ ⇐⇐⇐ has really great writers to help you get the grades you need, they are fast and do great research. Support will always contact you if there is any confusion with the requirements of your paper so they can make sure you are getting exactly what you need.
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

DevOps Practices: Continuous Delivery

  1. 1.
  2. 2.
  3. 3.
  4. 4. errors mistake unavoidable uncorrected • Defects are entirely avoidable.
  5. 5. Inspect quality in Inspect at each stage Build quality in
  6. 6.
  7. 7.
  8. 8.
  9. 9.
  10. 10.
  11. 11. billion billion • $365M cash & equivalents.
  12. 12. • Repurposed 8-yer old “Power Peg” flag.
  13. 13. • Manually
  14. 14. one of Knight’s technicians did not copy the new code to one
  15. 15. • 7 servers correctly using the old Power Peg code • 8th server sent cumulative child-orders in rapid succession.
  16. 16. • No • No uninstalled the correct SMARS code
  17. 17. • 4 million • 357 million • $460 million in losses
  18. 18. Execution Code Application Environment
  19. 19. pipeline • Automate deployment • Fail earliest
  20. 20.
  21. 21.
  22. 22.
  23. 23.
  24. 24.