In this chapter, we've created a much more robust deployment mechanism by building a CI/CD pipeline in VSTS. We started by disabling our original Git deployment mechanism in Azure itself, before creating a VSTS build to replace it. We saw that we have much more control over how our application is published if we need it, but also how simple it is to create a build if your requirements are fairly simple, like ours are.
We then enabled CI so that every push to the master Git branch of our source control repository triggers a new build in VSTS. Next, we created a release definition to connect to our Azure subscription and push the build artifact to our production environment app service.
We saw how easy it is to integrate VSTS releases with Azure app services, due to the built-in tasks that Microsoft provide. Finally, we optionally enabled CD so that every time a new...
