From the course: Azure DevOps for Beginners

Manually run and troubleshoot a pipeline - Azure Tutorial

From the course: Azure DevOps for Beginners

Start my 1-month free trial Buy for my team

Manually run and troubleshoot a pipeline

“

- [Instructor] Now that we have our pipeline, it's time to test it and see if it works correctly. So you click on it and then you can run it manually from the Dev Ops portal by clicking on this blue button, Run Pipeline. Once you bring up this dialogue you specify which agent pool, you specify which agent, which branch in the repository and other advanced settings, and then you click on Run. Now we've already set these when we were setting up the pipeline, but we can alter them and use alternatives while we're running the pipeline manually. This build, it takes about two minutes to run the builds, so I will cancel out, and instead we'll look at some of my past runs. So after I created this pipeline, I started testing it and you can see that I have some successful runs. I have two successful runs and I have five failed runs. Now let's prove it's successful. Click here. We see that it has the green check mark. And I can also verify this by going to the URL for the app service and see that my website is now running in Azure. That's our end goal is to build our product and push it out to Azure. So that's working. Now let's talk about the troubleshooting steps. When you have a failed build, you can click on any of these items and read details. For example, here, it says that I had trouble with .NET Core SDK, requires at least version 16.7.0 of MSBuild. The reason I got this error is because I had, I was using the wrong agent. So let's take a look at what I fixed. Let me go back to the pipelines. Click here. Choose to edit. And I had to make two fixes in order to get the successful build. First of all, I had to use this agent, Windows 2019. That's the one that has the correct MSBuild version. So I had to switch that. And the other thing is I started out by using .NET 5 for its website. We rolled it back to .NET 3.1 that .NET Core 3.1, I should say. And what the problem was is we didn't have the SDK available for the build engine. So I had to add an additional step to the agent. That's the step right here. The way you add a step is by clicking on the plus sign for this agent, choosing the agent, clicking on the add button when you find the agent you want, and then you come over here and you make some configuration changes. For in my case, I said, I was installing the SDK and that this is the version that I want 3.1 point. And then this is a wild card and I want it to install it into this folder. But now when I run the build, it's successful.

Contents