AUTOMATE APPLICATION DEPLOYMENT AND DELIVERY Azure supports a rich set of tools for going beyond the configuration and management of virtual machines, with tooling that brings automated builds and deployment, continuous integration, and testing in to your DevOps lifecycle. CONTINUOUS INTEGRATION (CI) CONTINOUS DEVELOPMENT (CD) CONTINOUS DEPLOYMENT WITH CI/CD Take advantage of continuous integration to improve software development quality and speed. When you use Visual Studio Team Services or Jenkins to build apps in the cloud and deploy to Azure, each time you commit code, it’s automatically built and tested — so bugs are detected faster. Ensure that code and infrastructure are always in a production- deployable state, with continuous delivery. By combining continuous integration and infrastructure as code (IaC), you’ll achieve identical deployments and the confidence you need to manually deploy to production at any time. With continuous deployment, you can automate the entire process from code commit to production if your CI/CD tests are successful. Using CI/CD practices, paired with monitoring tools, you’ll be able to safely deliver features to your customers as soon as they’re ready.
OPERATIONALIZE PAGE 107 aka.ms/practiceplaybooks Deployment Strategies While deployment of code through continuous integration and deployment tools often comes to the forefront with DevOps, there is a precursor, and that is the automated deployment of your infrastructure (or infrastructure as code). INFRASTRUCTURE AS CODE In Configuration Management , we focused on tools that can help you configure your virtual machines and infrastructure post-deployment. In this section, we will explore the methods and tools you can use to deploy your infrastructure in an automated manner and integrate that automation into a software development lifecycle. Infrastructure as code (IaC) is the process of managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. Source: The primary goals of adopting Infrastructure as Code (IaC) are: • Cost Reduction : By focusing on automation, you can invest your time and the time of your staff in the development and execution of repeatable processes. • Faster Execution : Through the development of repeatable processes, your time to execute builds drastically decreases and your time to provision resources becomes a known quantity • Risk Mitigation : With a well-known and tested declarative provisioning model, you know your environments are going to be deployed the right way, the first time, reducing risk through manual intervention. IaC ultimately leads us to a declarative provisioning model, where we define what we are going to provision We then can use imperative provisioning to control how that infrastructure is configured.
You've reached the end of your free preview.
Want to read all 127 pages?
- Fall '17
- Deniz Özdemir
- partner, Managed services, Azure Security, Azure Monitor