Join Paul Hacker for an in-depth discussion in this video Deploy into Azure, part of Continuous Delivery with Azure DevOps.
- [Instructor] Okay, so we're back here in our Azure DevOps environment. I'm going to click on all pipelines here. We're looking at a release pipeline that we created in the last set of videos. What I want to show you now is, I want to show you how we're going to release this into Azure. So in order for this to work, obviously you're going to have to have your Azure account all setup. If you haven't done that yet, go back and review the videos we just looked at and walk through and set up your Azure account and hook it into your release.
Now once all that is setup, I'm ready to test it out. Normally what I'll do, is I'll test out the release manually to make sure that it's actually going to deploy into Azure. I think, as you can see from my screen it looks like it's gone through all three stages successfully. It didn't start out that way, but we ended up with that. So there's always some little hiccups along the way, making sure variables are right, making sure resource group names are right, making sure slot names are right. All that type of information had to be setup. So the first thing I want to do, is I want to go and create a release.
So I'm going to click on this little ellipse next to edit pipeline here in the middle of the screen, and I'm going to create a release. And it's going to ask me a little bit of information. So basically it's going to say, click on a stage to change a trigger from automated to manual. Well this is an automated trigger, this is an automated trigger, and this is an automated trigger. Which means that when dev is done, it'll go straight to QA, it'll go straight to production. I could click on one and make it a manual, but we're going to look at a different way in which to manage that.
Down here it's looking at the latest version, you can select what version of the artifact that you want, in this case I had selected the latest version if you remember when I had setup the release. So it's looking at the latest version of the parts unlimited E2E build results, or build output that came. So we want to make sure we use that. So at this point I can create the release, now the only thing my release is setup to do is automatically deploy so when I create the release, if you remember before I said it's a two step process, you do a release and then a deploy.
So my release now has kicked off a deployment, if I click on release four up here, you can see it was manually triggered, these are the artifacts that are going here on the left, you can see in the center of the screen here we have in progress. I've already run through this once, but what I did is I went in and I renamed the resource group so that it would do a full end to end Azure deployment. Now this is going to take a little bit of time, because I'm deploying the whole infrastructure as we go. So you'll notice it initialized the job, it downloaded to our LinkedIn agent that we're using, and now we're deploying the infrastructure so if I go over into Azure and I go into resource groups and I do a refresh I should see this new resource group.
Resource group, LinkedIn Demo RG. If I click on that, you'll see in the center of the screen here we have this deployment section, and you can see down here at the bottom it's actually deploying some artifacts. If I click on the one deploying link, that'll actually show me a list of the deployments that are taking place on this resource group. And if I click on that link, it'll actually show me everything that's happening. And you can see here we've got a failure of some sort. So let's click on the operation details and see here what's failing.
Oh, because we already have the same name. So we can't just go and change the resource group name, so what I'll do is change it back in the variables, and let me go back to the parts unlimited E2E. We'll add the pipeline. That's the one thing about Azure, is you can't have the same named resources, obviously it wouldn't work that way. So we'll change that back to LinkedIn Demo like we had it before, and we will kickoff a new release from up here.
And we'll leave everything the same as we did before, and go ahead and create it. So this is release five. Now this will run a lot quicker because I already have the resource group here with all the resources deployed, and you can see three succeeded. But if I refresh this here, give it a minute, you'll see this actually start to re-deploy. And what it does is, it's looking at the template and looking at the type of deployment I'm doing, whether it's an incremental or a complete, and it's looking at the resource group and saying, do these all match? If not, if there is drift, let's fix the drift.
See there we go, we see one deploying. Click on that one, and you can see it's deploying out all the different updates that are needed if there's any drift. This will run a lot faster, in terms of an output. And if I look the timings here, you can see right now it's running just about a minute, most of it being in the resource group. So I'm going to pause here, and we'll come back when it's done.
- What is DevOps?
- Release pipelines
- Azure environments
- Azure Resource Manager (ARM) and ARM templates
- Deploying to Azure App Services
- Installing and configuring agents
- Running CI builds
- Creating a CD release pipeline
- CI/CD in action in Azure