Goad Signature Service Request with airSlate SignNow

Goad signature service request

so if you're just getting into the world of DevOps for the very first time you're probably trying to figure out CI CD pipelines and also perhaps containers building container images and deploying those and if you haven't done that before it could be kind of confusing so in this video I'm gonna show you how to build container images and deploy them through Asscher pipelines hey what's up everybody it's Mike five for Microsoft Azure MVP and host of the cloud skills FM podcasts this video is basically a step-by-step training it's from our DevOps class over at cloud skills IOR az 400 course and in this step-by-step hands-on lab I show you how to set up an azure devops project how to take a reference application that not only has application code also has an infrastructure code take that repository put it in Azure dub ops and then I walk you through building a CI CD pipeline that'll build a container image using the dockerfile in the repository and then eventually deploying that the azure app service I think you'll really enjoy this one especially if you're new the things like Azure DevOps and working with containers so what's going to get started in this first step of the lab I wanted to show you the sample application we're gonna be using and I also wanted to remind you about the yamo schema reference in the azure dev ops documentation and when you scroll down here the main thing I wanted to remind you of is the hierarchy of a gamma pipeline now obviously you're gonna have all the code for this but I realized that looking at an entire yamo pipeline is a little bit intimidating so just remember what we're gonna do here is we'll have one yeah Mille documents we're gonna have stages for the different phases of this pipeline so we'll have the first stage for build and tests so billing and testing the application itself and then we're gonna have a second stage that stage is gonna release the application into a staging environment and we're gonna keep this simple we're not gonna do multiple jobs in each stage we're just gonna have one job in each stage and each of those jobs is going to have different steps that have to take place along the way and this is nothing new from what we've seen in the past I just want to remind you that this hierarchy is very basic but it's very easy to get confused by this when you're looking at a finished yamo document so let me hop over to Visual Studio code and show you this application so we've got two things in this repo when you're going to import this into your project so there is the application itself this is a visual studio solution that's got three projects in it we're gonna make use of the actual application itself the asp net core web application and then there's a unit test project in here so in this arm templates folder we have a template here to build a web app in Azure app service and then there's also a template that will deploy a container registry resource so the cool thing about this implementation is that the pipeline is going to build the infrastructure for us if it doesn't exist using the arm templates and it's gonna do that as part of the build pipeline so that's the overall basic project structure for this application let's go to the next video and we'll start digging into the azure pipelines yeah Mel document let's go and break down the pipeline yanil file that we're gonna use to build the CI CD pipeline so along with this sample application you'll have an azure pipeline the animal document let me go ahead and move that over to the left here and this is gonna be a very simple implementation just a couple stages as we've seen in the past we're gonna have continuous integration setup so any changes to the master branch of the repository are gonna trigger the pipeline and so as usual we got a handful of variables here I have my build configuration variable and I've used the location variable I'm gonna use this in various places throughout both stages to indicate to the tasks where I want to deploy my resources so there's a variable for the location for the region we're gonna use there is a variable for the ECR hostname so the azure container registry hostname and obviously you're gonna want to use unique values here so as you basically import this repo i'll show you how to do that later but you're gonna want to change these pieces of information so these are all dns names at the end of the day for the most part so i'm just going to change these values we'll say this is the fifth version of this that I'm implementing here you can use anything you want as long as it's compliant for a DNS hostname so your ACR fqdn will be listed here just the hostname will be set in this variable the name of your resource group will be included whatever you want to name the docker image so it's going to get stored in the container registry and then finally the name of the app service web application so remember that just like any kind of programming environment we don't want to hard-code any values if we can help it and especially we don't want to repeat ourselves so you'll see in this AML document that we use these values multiple times but then also not hard coding it in the configuration is a nice practice and it gives us more capabilities going forward my things so after defining variables we have our stages declared and again we're just gonna have two stages and you can basically see here that we reference the first stage giving it a name called building tests notice I'm using comments along the way as well and the properties for this building test stage we're gonna have one job job is gonna be called building tests and we start basically configuring all the things that we've been looking at throughout this program so in the hosted pool we're gonna use a virtual machine running Ubuntu 1604 since this is a dotnet core web application this is cross-platform so we can do the build in tests process on Linux and for this job we have a collection of steps just under the steps indicator here you can see that we've got our first task so this first task is actually going to deploy our infrastructure for us this is the azure resource group deployment task that we use to launch armed templates so inside our project we're going to be expecting to have a service connection so this is going to be something I'm going to need to create you'll see me do that later here you can see that we're referencing the resource group name based on the variable it's included to the top of the ml document same thing about the location and then the file that we're gonna use to do the deployment so the actual arm template itself so in this build stage we're building the container registry resource that should happen pretty quick and if it already exists it will basically be a quick update as well because we're doing incremental deployment here by default and notice this input here for this task override parameters so these are the input parameters that we would actually be using from the command line if we were doing an arm template deployment and so what you'll notice here is instead of using the parameters file that's basically part of the arm template system we're just feeding in the parameter values and here we're using variables in Azure pipelines so we're able to take the variables there at the top of this document and reference them inside this override parameters value here and the one thing I wanted to point out is that sometimes when you're using variables that have a space like location how it has west space u.s. space to in the value and you're referencing that somewhere else like right here we know that from the pass this macro syntax of referencing a variable value can be done by using a dollar sign and open and closing parentheses with the variable name inside it but if that value is going to end up returning a string that has spaces in it like in this case West space us space - you want to enclose that in double quotes just like you see here and so that first task is going to take care of deploying the arm template the second task is just going to do a dotnet restore just like we've seen in the past so the command to do a dotnet restore we're gonna then do a dotnet build and then we're gonna run our unit tests so again we're just using the.net core CLI tasks here to do all these things after we execute those unit tests we'll publish the project files we'll go down here we'll use the docker task to build a container image so this would just be like on your desktop on your machine and a terminal running docker build notice that we're going to reference the container registry that we've got listed in our variables and then we're going to define an image name that we're gonna use for this container image so here we're using our own custom user-defined variable called an image name and then for the tag we're using a variable from Azure pipelines which is build that build ID so every time a build runs this build ideally difference and that'll give us the ability to incremental e-version each image for the docker container from there we'll use the docker task to go ahead and then push that image up into the container registry so the command for this is called push an image in and again we're gonna reference the same image name with the same image tag basically the build ID and the last two tasks in this build and test stage are to copy the files so the arm templates into the build artifacts staging directory because we are going to do an arm template deployment in the release stage to deploy the web app infrastructure and then finally once that stuff is copied over to artifact staging directory we're just going to publish those build output artifacts in an app called app so that is the build and tests portion of the CML pipeline let's go to the next video and we'll take a look at the staging release that's actually going to deploy our application and get everything up and running alright so now that we understand the build and test stage here in the CML pipeline let's scroll all the way down to the bottom to the second stage and we'll just talk here about this release stage so what we're gonna do here again is we're just going to specify one job this is going to be a release job again we're going to use ubuntu server out of the hosted pool and then in terms of our steps this is gonna be very simple so we've seen this in the past remember we're gonna not check out the repo in this release process because there's no need to do that we're gonna have access to the artifacts from the build stage so we can actually download those build output artifacts so we can reference those here and then finally when you get down to the last couple of tasks number one we're gonna again use the azure resource group deployment task to launch an arm template and as you can see we're setting the resource group name through a variable the location and finally the path to the arm templates itself is listed here keep in mind that when you're working with tasks in a release pipeline like this or a release stage you can reference the pipeline dot workspace here using this system variable that's available to us to get to your build output artifacts so we copied the arm templates in that last couple tasks in the build and test stage that's going to put those eventually in the output artifacts we can get to them by referencing this variable here finally this task also has some override parameters so there is no parameters file with that arm template and then we're just specifying the inputs here finally the last task in the release stage here is we're just going to do an azure RM web app deployments we're going to deploy to app service so we've seen this task in the previous lab but we're doing something a little bit different this time we're deploying a docker container so the inputs are just a little bit different so we're gonna set the service connection in this case the app type is going to be a linux app service environment and then when it comes to indicating the web app name this is part of our variable declaration at the top of this documents we've got our doctor namespace property which is going to be set to the ACR hostname itself the docker repository is the image repository we created when we're pushing our image up into the ACR environments and finally our docker image tag now the cool thing with this task that you might find useful is there is a web app URI property so you can create a variable that's going to be available inside the pipeline after the web app has been built so this task is going to build a web app and once it's complete we can populate the web app URL variable with the URL to the app service that way you could add a subsequent task after this go off and maybe do some testing against that URL do some UI testing some performance testing things like that so that's everything we need to take a look at for this yeah Mille pipeline let's go to the next step in this lab and I'll show you how to set up the project and get this application setup and going so back in the azure devops portal let's go ahead and create a new project here it might call this docker app service so we'll create this project and what we're gonna do is import a repository from the cloud skills github organization so over in github calm slash cloud skills there's this project here asp net core demo or actually it's asp net core docker demo and you can see it's the same files that i was just talking about here so let's go ahead and grab the clone URL for this and inside the project will go to repos scroll down to imports and then we're going to import this repository and now that the import is successful let's go to our project settings on the left-hand side and it will scroll down let's go to service connections it will create a new service connection for this application and this project so we're gonna pick resource manager here and click Next and we'll do an automatic service principle now I'm just gonna scope this at the entire subscription level here and we'll call this a sure SC for a service connection and with that service connection configured let's go back over to the project configuration will go to repos here's all of our code everything looks good and so let's go ahead and setup the pipeline will click on setup build and then we'll scroll down here and we'll say we're gonna select an existing Adger yamo file inside this repository so we'll pick the azure pipeline zml documents click on continue and here you can see that we've got all the code that I was pointing at last time so notice remember you're gonna want to replace the values for this so if you import this you can go over to repos you can of course clone and download it on your machine but you could also just come in here and edit it and so you just want to make sure that you're using unique values here so I'll change this to CS web app docker 0:06 I'll commit those changes to the master branch and when we're looking in repos I can set up my build selecting existing as your yamo pipeline and then now that that's been updated everything looks good there let's go ahead and run this pipeline so down here you can see that we've got build and test and staging and this is very similar to the lab that we took a look at in the last week of this program the only difference is this build process is first going to create a brand new resource for us it's going to create a container registry instance which I don't currently have and then it will build out the infrastructure that I need for app service so let's give this thing a second to run and we'll see what happens all right so it's been in just under ten minutes both the build and test stage in the release stage are done so we've got a brand new application in under ten minutes here from scratch going over to the azure portal here is the resource group and here's my app service plan my web app itself app insights resource the container registry let's go into the web app itself and then let's head over to the URL for this application so we can see a success message this thing is working great and this is running inside a container inside app service so it's last up to this lab let's move to the next video and then we'll see how we can update this application as a last step to testing this out let's change the application just make sure that that kicks off the pipeline and indeed does update our application so this should not do anything to our existing infrastructure so we have this infrastructure now but let's take a look at updating the app watching the pipeline executes and updating this infrastructure with the new container image so let's go over to repos here we'll go into the application folder we'll go to this first project asp net Cornette core and then inside pages we'll go to the index page and then we'll edit this and so on the home page where it usually says success will update that to say success you have deployed via Azure DevOps and so let's go ahead and commit that change to the master branch which will trigger our pipeline and then we can monitor that by going over to pipelines here on the left and let's let this run and once this is complete I'll show you what happened in the resource group all right you can see a few minutes later everything looks good building tests and staging deployment is complete let's go over to the azure portal and in the resource group let's first check the web app so we'll the app service will go to the URL all right and so as we can see here the success message is on the page everything looks good let's close out of this and then let's go back into the resource group let's go to the container registry resource and then here on the left hand side if we go to repositories we look at this repository we can see that we've got two different container image versions one that's in there for build 145 and one that's a never build 146 that's the most recent one that we just deployed into app service so it brings us to the end of this hands-on lab I hope you enjoyed it and I will see you in the next one [Music]