Improving Code Quality with Branch Policies, SQL Change Automation, and SQL Provision
DevOps isn't just about deployment tempo, it's also about using automation to help identify problems in code as early in the development process as possible. In this demo, Redgate's Kendra Little shows you how a branch policy in Azure DevOps can kick off automation every time a pull request is created. This, combined with Redgate's SQL Change Automation and SQL Provision extensions, allows you to validate that your code builds successfully and all dependencies are met right away. Following this, the automation uses cloning and automated deployments to create a secure, production-like environment in which the pull request reviewers are set up to thoroughly validate the changes proposed in the pull request.
01:42 - Demo overview
02:25 - Where to find branch policies, what they are, and how mine is set up
06:37 - Checking out a feature branch and making a change in SQL Change Automation, then pushing it up to the repo
10:14 - Creating a pull request in Azure DevOps, which automatically kicks off my build pipeline (thanks to that branch policy)
10:58 - Watching progress of the build pipeline in Azure DevOps -- this uses the SQL Change Automation Extension
11:51 - Showing that the pull request has also automatically kicked off a release pipeline after the build
12:23 - Showing the pull request trigger inside the release pipeline, and the tasks inside the pipeline: clone a masked copy of production data, create a release artifact against the clone, and deploy the changes in the pull request to the clone
14:45 - Showing the environment that was automatically created and deployed to for quality review of the pull request