BluePrint Diagram & deploy stage of CD

2.7. BluePrint Diagram & deploy stage of CD:

• 
  Once we have a built a runnable instance of our code that has passed all predefined tests, we’re ready to deploy it. There are usually multiple deploy environments, for example a “beta” or “staging” environment which is used internally by the product team, and a “production” environment for end users.
  
• 
  Teams that have embraced the Agile model of development—which is guided by tests and real-time monitoring—usually deploy work-in-progress manually to a staging environment for additional manual testing and review, and automatically deploy approved changes from the master branch to production.
  

2.8. CD – Benefits:

• 
  Eliminate DIY for Continuous Delivery and increase the focus on the product.
  
• 
  Automate the repetitive tasks and focus on actual testing.
  
• 
  Make deployments frictionless without compromising security.
  
• 
  Scale from a single application to an Enterprise IT portfolio.
  
• 
  Connect your existing tools and technologies (such as CI providers, DevOps tools, or scripts) into a harmonious workflow.
  
• 
  Integrate teams and processes with a unified pipeline.
  
• 
  Create workflows across the development, testing, and production environments
  
• 
  Provide a single view across all applications and environments.
  
• 
  Ship both cloud-native and traditional applications in a unified pipeline.
  
• 
  Improve overall productivity.
  

2.9. What is meant by Continuous Delivery?