Azure DevOps CI/CD Pipelines Step By Step Tutorial | Azure DevOps Pipelines Tutorial | ScholarHat

hello everyone if you are new to the Azure devops and you want to learn how to create a end-to-end CI CD pipeline for your project so this video is for you in this video first I will tell you about what is the CI CD pipeline how to set up it in Azure devops how to start a application from scratch and how to deploy it on Azure with the info sezio devops CI CD pipeline if you are coming to the Channel first time a request to you please do subscribe to our YouTube channel and click the Bell icon so that the information about such valuable videos you will get notified so let's get start with the video now let's understand what is continuous indication so continuous integration means it is an integration of complete code in the common Repository which is shared across the team obviously when you're working on a project so a team of the developers is working on the project and the developer team commit the changes to the source control it can be the Git it can be the GitHub I like it can be the TFS so every time when the developer is committing the changes So based upon those changes we should trigger the build or you can say we usually trigger the build so that we verify whatever the changes has been committed so far so when they are going to integrate with digesting code so there is no error while building the application send the continuous integration the flow is here V having the multiple developers in the team and when a developer will commit the code that code will obviously committed to the Version Control repository like get DFI select GitHub and we having a continuous integration server This Server automatically pull the committed changes recently the developer did and based upon the changes it entirely built the application and what are the test cases we are having behind the scene those test case is also going to be checked over there if everything is working fine so it further proceed to the next level for creating a build or you can say for providing the build to the release pipeline if there is any error in build process so it will provide a detailed report to us like this is the point where the build has been filled so continuous integration is actually a important thing when we are going to commit the changes and we are going to verify whether the changes are committed by the developers are going to impact the entire build life cycle or not so in summary The Continuous integration is all about to build the code whenever a developer commit the changes and based upon the community changes you provide us a detailed report whether it isn't been successful or whether it has been failed so this is about the continuous integration you should know continuous delivery continuous delivery The Next Step for the continuous integration so what happens when the developer is committing the changer to the Version Control repository so from there the ca server pull the changes and build the code and try to pass all the test cases if all the test cases are going to pass as per the business acceptance so we can deploy the code on the production environment what are the environment you are using for deploying the code so you can deploy the code to that element environment you can apply the code to that staging environment or you can apply the code to the production environment so after the continuous integration we deploy the code to the specified environment over there so this is about the continuous delivery now let's understand the continuous delivery and continuous deployment how these two things are different from each other so when we say about the continuous delivery in case of continuity after the staging deployment to the to the protection machine we do the manual deployment that means after testing everything in the development stage then in the testing stage then in the staging server when we are sure everything is working fine in this spring Targets in this release we manually deploy to the production machine so this is the practice we follow in the continuous delivery process and if you will look at in the continuous deployment so continuous deployment there is a automated deployment of the release to the production machine so basically we having the some checkpoints over there we are doing the the substance test cases if the all the test cases are going to be tested arguments are going to be verified at the staging environment so it automatically deploy a release to the production server so if you are following the automate deployment to the production server it is continuous deployment option so this is the difference here between the continuous delivery and the continuous deployment So based upon the requirement you can use the continuous stream layer or you can use the continuous deployment so usually we prefer the continuous delivery option before deploying the code to the production environment we manually check all the things and finally when we show everything is working fine we reply to the production server so for cutting Azure pipeline so first of all we need to create a Azure web app after getting the Azure web app we will create the project using the widget Studio so that we can configure it with the azure devops so let's first create the Azure web app later on we will create and configure the Davos project or then we will create the project over there using the video Studio so make sure you are having the Microsoft azure portal access so you can subscribe to the Microsoft Azure and then you will have the access to the Microsoft Azure portal so what I'm doing here I'm just going to create a resource over there and here I'm just looking for the web app so here I'm just going to create a new Resource Group so let me create this new resource room d and d r g is my Resource Group and here I'm just defining my app name let's say DMT web app is already taken by somebody else so let me take the refer name so DNT web app devops so this name can be anything but make sure it is unique in the selected reason Central us so I'm just using here the runtime stack so as a runtime mistake I'm using here is.net core uh 3.1 base application we are just going to deploy so just user.net core 3.1 and here we can deploy the code as well as we can deploy the docker container so I'm not willing to deploy the docker container that's why I'm using here the code option then you can select the operating system Linux and windows so I'm just using here windows but again go ahead with the Linux also then do select here the windows plan so here this is suggesting as the plan name so this plan name can change it's up to you about the plan name you're willing to give it let's say DND web app so this is my plan I'm just going to create over there and from here you can decide that SKU and the size also so let's say I'm just going to start with the standard plan S1 even you can select the other plan also which is available as 2 S3 S3 and we have P1 P2 and P3 so let's go ahead with this one also the next option here for monitoring if you're willing to monitor the application we can enable or disable it here so write down node enabling it is disabled here because it so here whatever the the runtime stack we have selected that is not supporting actually the application inside so that's why we are not able to mentioning yes so make sure you are selecting the proper run time to use it let's go to the next option for tagging if you're willing to put over the label so label I'm not putting over there now let's review the changes before creating it so let me create it now so it has been submitted for the deployment after some time it will create the web app and guys here if you have link to learn the web in the details so on the dotnetics we already having your codes on Microsoft Visual fiber so if you're willing to learn all the expect of the Azure web app we can refer this clears creating and managing the Azure web app here explain the different types of web services everything explained in detail so I suggest to here you should refer this course to understand the Azure web app in detail so you can see the deployment has been completed let's go to the resource to verify everything has been completed so right now it's having a testing web page let's browse it is showing me a app service Developers the app service is apparently so perfectly it is working fine so now our web app is ready now we need to create the devops organization so that we can configure the devops organization for the Azure apple and what various other things creating and conferring the Davos projects so far what we have done we created Azure web app using the Azure portal now what we need to do here using the devops portal we need to create a devops organization and there we will create the DeVos product so that we can start building rasp.net core application and without the changes we are building the local machine we start pushing to the Azure app over there later on we will build the Azure pipeline so last time we just log into the portal.co.com this time we will log into the dev.seo.com so we having a site Dev Dot as your.com so to login into this rap.seo.com make sure you are having the Azure devops subscription so you can sign up here at free of cost even you can use the same email ID which you are using for this Azure portal subscription same can be used with the Azure devops also some login with the same email ID so let's see I'm just using sign into the SEO tab box so you can see here I'm already having here few organization which I created for learning purpose let's say for training purpose so now let's do one thing here let's create a new organization I'm just going to create it from scratch so let's continue to accept the condition and here it is just suggesting the new organization name so what I'm doing here I'm just going here the new organization name but the application we created sub to you what the name you're willing to give it here I'm just using let's say D and D app ort let's say this is my organization name let's say DNT org app so this is the pattern name here and within a organization you can have multiple projects over there now you can Define The Host location like where you are going to host your project it can be in India it can be outside India also so let's say I'm just using a South India as a location for hosting this project over there let's continue so what it is doing behind us and it is creating a new devops Organization for us but the given name so now you can see the organization has been created the name is here DNT org apps so here we can have multiple application so what we need to do here we need to create a project over there so I'm just defining the project name exactly the same as we Define our web opening so this is a DNT web app DeVos project but you can have different name also so I'm just defining it D and D web app let's say just just mention it DNT fiber then you can Define the visibility like public and private so in the public like anyone can access it but here this project I'm not trading here for as an open source project I'm just creating it for my personal use unlike it's an organization label project so it should be private so let's just click on this Plus icon button so that we can create the project so now it is creating a new project for us so now the new project has been created so you can see we having option here for board we are being option here for repos pipelines test plans and artifacts so these are the various offerings the Azure devops is offering to us so here I'm not just going to cover here board and other things we just focus here on the wrappers and the pipelines so so two things we are just going to cover over there so let's go to the wrappers over there and if you look at I don't have anything set up right now so it is a new wrapper we need to set up so they're just giving us a URL so using this URL I can set up this one in my local machine using either vs code either using the widget Studio so what I will prefer here I will prefer here just copy this URL and now just open the widget Studio 2019 I'm having a gist 2019 and this was just 2019 we having the option clone a repository so just use the option here clone Repository now just paste that copied e URL now Define your local path where you are willing to clone that repository code so I'm just going to select here my local folder so let's say I'm using a desktop and let's set this here we having for code and I'm using let's say I'm just creating here a folder for the devops any folder you can create over here it's up to you and here let me select this folder over there now this is option here to clone let me clone it so what it will do it will clone everything from the Azure wrappers to my local machine let me mention here your devops I'm mentioning my credential over there now I have just signed in over there so if you look at here after some time you will get to know the other thing has been sync from the Azure our devops project to the local machine if you look at it this is my folder which is available if you will browse to this location we have in your open folder in File Explorer so this has been added a right notices containing only one folder dot vs so this dot vs folder is containing with few settings over there project settings and the sqlite file it is containing here so this has been set up completely so now what we need to do here at this location we need to create a new project so it can be a asp.net core application it can be used for an atomic E5 application now we will set up it here and finally we will push the code to the Azure wrapper what are the wrapper we are having so right now we don't have any code in the wrapper because we have not created any project in the local machine and even we have not pushed that code here so in the next video I will show you here how we can create the project and how we can push it to the Azure wrappers over there creating a sprout net core project so far what we have done we just created a devops organization and then we created a project so now that we need to configure with the local machine so already we just map the devops project with a local folder and in that local folder we need to add the esportnet core base application so let's see how we can do it here using the widget 2019 2019 as we did last time and make sure you are having the home for the devops if sometime it happens you are not able to find out the credit folder which you have done in the seat right you can go ahead to the back location and they will find out all the available connected services so you can see I'm having here Azure Dabo some mapping here GitHub and you can see the local machine I'm already having the devops so make sure you have already installed here the git for the windows so make sure you have installed the equip for Windows to configure it properly so in my case I have already installed the git for my windows but you need to install it if you are using the Mac so make sure you have installed the git for the Mac so I have already installed the git for Windows now I'm just going to create I'm just going to go into this devops mapping in a local machine what we are having now there is option to create a new project click on the new button now here I can select base.net code template click on the next button Define the project name let's say the project name is here DNT web is my project name and make sure you are using the same location let's say C drive code and the DeVos now let's click on the create button to proceed further and here we will find out all the available templates which we can use with the escrow.net core application and right now if you look at the latest version I'm using here is.net core 3.1 but later on you can have the inspironment 5 Base product net 6 so it doesn't mean what the version is there you can select over there the version I'm using your MVC template to create my Sprout net core MVC application and here I'm not using this ttps let's go ahead with only HTTP now click on the create button to create my export net core MVC application with all the necessary settings and if you look at what the code has been generated the code has been generated like this way we have been here DNT web app and it is containing other solution like this way DNT web app then we have been the solution inside this DNT web app folder so what I need to do here actually for the easiness purpose this entire things we need to move to the at this folder label at the one label above I need to move it the things so before committing the changes let's do a minor change over there because I don't want to face an issue at the time of build so let me cut the things from here and put it at the one label above here so everything is available now here and at the root level we having the DNT web app solution so I just closed my widget studio now let me open it again so these are a trick you need to do here because it will help us when we are going to find out the low the location for the solution file now you can look at the changes what are the changes we have done in the local repository all the legendary will find out over there so you can see all the files which we are going to add it is showing me in the list over there so these files are going to add over here like csis JavaScript file CS file everything that is going but before committing the changes let's make sure everything is running fine in my local machine so let me test it first then I will post the changes to the Azure repose so now you can see here the every application is running fine over there so now you can see here the application is earning fine without any issue so now let me push these changes to the Azure apples so here I'm just using here my changes to team Explorer then Define here a message initial then you will find out here the option the commit all so commit all will commit the changes to the local wrapper not the cloud wrapper then we having option A commit all and the push so commit all in the push will commit the changes to the local map of us then those changes it will push to the Cloud rep also so let's use this option commit all in the push so that in the one case it will commit the changes to the Cloud app also now let me check it out at the azure devops organization whether we having the code at the repo label or not let me reload the code over there and now we can see here I'm already having the now code over there so what are the code we have in the local machine now we first successfully reply to the Azure devops Repository the code is available over there now here we are ready to set up the build pipeline so this is option here for the pipeline from where we will set up the build pipeline demo for creating a Azure build Pipeline with Azure web app so right now we created the esportnet core web application now let's see how we can create a build pipeline Avid alphab is your web app and the azure devops so what I'm doing here this code we already checked in to the Azure appos and it is available over there now this option here for Azure Pipelines and in the Azure pipeline we have been the option to create a pipeline over there now here if you will look at we can create the various types of pipeline we can get the pipeline for deploying the code to the staging environment we can create a pipeline for deploying the code to the production environment but here I'm not creating the first release pipeline first we will create the build pipeline later on we will create the release pipeline so what I'm doing I'm just going to create a pipeline for the build process so there is option here it is suggesting us like where your code is available as your repo git are we having a some other option also like GitHub we having the GitHub Enterprise Edition also and if you look at we having a two style to create the pipeline we having the emulator style and we have been the the classic editor Style here to make it simple I will use the classic editor Style but because in the classic editor style we having a complete GUI based interface where we can just select the things and set up it easily in the some other course I will talk about how we can configure what does your pipeline with the help of EML so the EML we need to write the code so I'm just using here the classic editor to make it simple in the classic editor we have been the option here for Azure wrap pause kit so we obviously we are being the git repository over there so what all the repository we created over there by default support bracket but you can have the support for the DFS also but in this case I'm having the git so this is my team project this is my repository and what branch you are using so we're just using the master Branch we don't have any branch but sometime when you are dealing with the multiple Sprints are like multiple uh the story over there you can have the multiple Branch over there but in our case we having only one branch Master branch that means like the master Branch then click on the continue button notice asking for to configure it using the ML and using the built-in template so we having a template as your web app for asp.net and we having the others template also we have been the the template for asp.net core web application also so it's up to you what the template you like like where you are willing to deploy the things so I suggest you here you should go ahead with the template here as your web app for asp.net if it is a mvc5 application application so what I will prefer here I will prefer here is protonet core template let me select this template over there now if you will look at here in this template there is a agent by default it is suggesting here a agent offered by the Microsoft Azure itself so we don't need to worry about the agent is the part of the Azure pipeline then these are the steps already defined over there so we having the steps to restore all the dotnet core packages then to build it then to test the test cases then we finally having the option to publish the code and finally we have been the option to publish the artifacts so as a output from this pipeline we need the artifacts and this artifacts further we will use in the release pipeline to deploy the code either to the staging environment or either to the production environment so here we are building a build pipeline not the release pipeline now we can Define here is this build pipeline name so here it is by defaults adjusting the build pipeline name as we have been the project name and it is having a CI CI here for continuous integration now this is the as agent pull you can select over there so you can see we having the agent pole here that is your pipeline and it is using here that is your pipeline is in pole if you are having your own agent pool you can select over there but in the Azure Davos portal we having the diff or the agent provided by the Microsoft Azure itself so those of them we are using but you can use here your custom agent also this is the agent info specification over there so this agent is running from the Ubuntu machine it can be run from the windows and the Mac OS Also let's go ahead with the Ubuntu machine so don't worry about that one so what is happening agent is a processor link on the Ubuntu machine to perform all these tasks over there then it is looking for the C sharp project so the C sharp project if you will look at the part of this DNT web app this is a C sharp project and this is the path we need to mention over there so in the path over there we just mentioned then we having a path for the test project so right now we don't have any test project over there we have been only C sharp project where it will look for now we have been the option here for Save and queue so first option here only save another option is here as soon as you will save it it automatically initiate that build pipeline so here before saving and gear let's check it out the other option also we have been option for variable so if you are willing to define the variable for let's say the database connections thing anything so those can be defined over there we having the trigger also over there if you look at we having the trigger here to enable The Continuous integration continuous indication means every time when I will be checking the code it automatically initiate the build for the code so if you remember in the PPT we just discuss about the continuous integration this one so to enable The Continuous integration in this build pipeline I need to just check this checkbox so let me check this checkbox to enable The Continuous integration to the master Branch so every time when the developer will commit the code it initiate the build pipeline for us and we having the other options over there where we can Define the settings related to the or build properties on another this is a retention policy and we have industry so right now we don't have an history so these are the other options you can Define over there for your build pipeline let me say 1 Q Now define the same comment so it is my first commit I'm just using here initial agent pull as your pipeline this is the agenda specification this is a branch this is the variable let me save and run so now it has been scheduled over there you can see it is showing me the this icon means this job has been now queue let's wait it and here you can check the status also how it is running so you can see it has been initialized now to check out first step has been done properly not just trying to restore all the packages and here on the console window it will show what is happening behind the scene so it has been restore successfully notice trying to build my code over there so build has been done test has been done because we don't have any test cases now it is trying to publish a artifact so you can see as an output I'm having here one artifacts let me successfully I am able to publish my code as an output I'm mapping the artifacts if you are able to get this folder that means the code has been published so this is the publish folder which you can download and check it out whether it has been published successfully or not I have downloaded it let me look at in this artifacts folder you can see it is my same publish folder as we publish in a local machine so when you will try to publish your code locally you will find out all the code in the dll form even all the aesthetic files which are the part of the WWE root you will find out over there so before creating the lease pipeline please verify this artifact folder properly so in my case it is perfectly generated now we can go ahead to the next step Azure release pipeline so far we have successfully created the a build pipeline now let's check out how we can create the release pipeline based upon the environment also so if you look at here usually we create the list pipeline to the delayment environment separately then we can have the euat then we can have the production one it's up to you how many stages you are willing to create over there even in place of the dev and the eot you can have the staging also so what I'm going to do here in the web app I don't have any environment whatever the web app I'm having over there so if I will create a release pipeline so that directly deploy the code to the production environment so to create the stages over there let's go back to the web app and let's create the slot or you can say let's create the environment in the Azure web app for the study so I'm not going to create the environment for the development and the testing I like uat I will create the environment for the staging over there so let me login to the portal over there and let's create a slot in my DND web app so this is my DMT web app devops and what I will do here I will create here a slot there is option here deployment slots in the deployments load I need to look at how many slots are there you can see I'm moving only once load for the production let's add a new slot so this new slot I'm just getting here for the staging is stating this way then there is option if you want to clone anything um let's say I'm not going to clone anything over there let me create it so it will create a one new environment for the studying so what we will do when we will create the release pipeline first we deploy the code to the staging environment and there we will test it when it will be tested over there completely then we will move to the production environment so you can see the staging environment has been created over there now in the next video I will show you here how we can create the release pipeline for the staging environment over there demo for Azure release pipeline for the staging environment so let's see how we can design a pipeline to apply the code to the staging environment so if you look at here this is my Azure Pipeline and just go to here the releases option right now we don't have here any release pipeline that we select the option new pipeline to create a new release pipeline over there now here we have been the Buddhist templates one of the template you can use as per your requirement so we having a race for.net application so I will use this template but if you are having a node.js application Python and the PHP application so another template you can select so let me use it as your app service deployment template I just applied over there now Define the stage name it is here staging because we are just going to provide the release to the stating environment now let me add the artifacts because ultimately we need to provide the published code so if you remember in the build pipeline we just received the artifacts folder that artifacts folder I will add here as a input so that it will deploy the that artifacts to the staging environment let me selected artifacts then we have in the project then use a source as a that build a name and just look for the always the latest version we added over there then here we having a trigger so from here I can enable The Continuous deployment so you're having the two option either enable The Continuous delivery but in case of continuous derivative it would be the manual trigger but if you will mention our continuous deployment it would be the automatic trigger so let me enable here the automatic trigger so right now it is disabled it's a manual let me enable now it will become the continuous deployment automatically let me close it after enabling The Continuous deployment now let me configure the job over there in the job it is asking for the Azure subscription so make sure you have logged in over there so in my case I have already logged in with my Azure subscription account credential if you have not logged in please log in and authorize it so let me select here my subscription it is with your student Enterprise in your case you need to log in if you have not logged in over there then hit a web app on the windows so this web app actually we created using the windows environment so that same I'm selecting now let me selected the app service name so this is my app service name over there and actually this code we are just going to deploy to the staging environment but here I'm not getting any option to define the stage environment so that option you will find out in this option so here that one setting you can find out over there deploy to slot our app service environment same thing I'm just going to do here I'm just going to deploy this code to the resource Group D and TRG and by default you can see it is selecting here this Lotus production but let's select a slot as staging not the production so X perfect this is the only thing you need to mention over there let me save it then you will save it it will ask for the comments let's define in the the comment for initial commit for staging anything which the message you are willing to mention you can mention over there so this is my first release pipeline I'm creating for the Stadium environment but this information after saving can find out in the release pipeline so the from here actually you should change the release pipeline name also let me change the pipeline name that says staging pipe line so that you can remember it we just save it so we just renamed it renamed okay so let's go to the all pipelines if you will look at in the whole pipeline we are being a one pipeline over there with the name staging pipeline so so far we have not provided any release in this staging pipeline so you can see it is empty right now so let's now let's provide the release to the studying environment so there is option create release and here it's a automatic trigger so I don't need to mention anything I need to just create a release so we already having a code into the publish artifacts it automatically start releasing so just initiate the release I'm just adding here my comment initiate my release let's create it so you can see here it has been queued automatically because it's a continuous deployment so let's wait even you can check the progress over this release Here it is trying to connect and after view while you will look at here the console output about the status of this release so you can see here the job has been initialized now it is showing the all the status here one by one so please wait so it is downloading the artifacts from the build pipeline now it is started to deploy to the staging environment so you can see it is showing me the packet deployment using the zip deployment initiated that is trying to deploy the code to the staging environment over there and you can see it is successfully updated the app service and it has been done successfully over there so you can go back to the pipeline and the stage status you will find out it is succeeded so this is my staging pipeline status so we have provided only one release so far enough you will check it out whether it's the code has been deployed to the study environment or not let's click over there then browse to that file to that website sorry if you look at this the website is trying to open and you can see I'm having my Ace product core deploy code which we tested locally so we have in the Privacy we are being the home page so everything is working fine over there so this way we successfully deployed our code to the staging environment using the Azure release pipeline Azure release pipeline for the production environment so let's see how we can create Azure release pipeline to apply the code to the production environment so if you look at here we already having a One release pipeline for the staging one so either I can edit the existing one either I can create the new one so better wise here let's create a new pipeline I'm just getting here a new release pipeline for the production one and here we will follow the steps so here first we deploy the code to the staging one then later on we will deploy the code to the production so trigger you can decide whether it can be manual trigger whether it can be the auto trigger over there so let me Define here the first this Azure app service deployment and the stage name is let's say staging so first we deployed the code the staging one Define the artifacts location let's say build use the latest version over there and Define the quantizer deployment trigger perfect similarly let's define the jobs for the staging one so as your subscription are the news here the app service name so this is my app service name over there and let me Define here that slot name because first we are going to reply to the standing one so slot is here and let's say studying so these are changes make sure you have done of the slots let me save it and it is here for staging slot so we added it here let's go back to the pipeline now let's rename it let's say a release pipeline for production one so I'm just using a prod release pipeline this is the way I just rename done this one let's say Broad release and here we can add a one more step just next to the staging one there is option here add a new step I'm just using here Azure app service deployment let me select it Define the stage name here product for production I'm just using it let me close it and here let me Define the job same here Define the subscription over there Define the app service name it is here DNT web app and this time I'm just going to reply the code to the production one so I don't need to set up here anything because it should be to go to the Productions load by default let me save it now so it is here production plot so let's go back to the pipeline so you can see this is the option available here for a staging we are being for product also now we need to understand here the deployment to the production environment so if you look at here there is a two option here manual one and we have been here Auto so the manual it would be the continuous delivery and if it is a automatic then it would be here continuous deployment and if you look at right now it is here continuous deployment so as soon as the the staging stage would be completed it will start deploying the code to the protection slot so this is a trick it's happening over there if you need the manual tree of the news here the manual only so need to select this option if you want to support here this continuous delivery but I'm not using the quantities daily I'm just going to use a container deployment so this way I just use here automatic trigger over there so this is the way how you can verify whether it's a continuous deployment whether it is a continuous delivery so now from this pipeline I can create a release to verify like the code first will apply to the staging one it will pass through the study it will applied to the production one let me create a release pipeline where I'm just going to use here for production one let's click it so release has been created over there if you look at it has been first queued to the staging slot you can check the logs over there so you can see it is in progress and it is showing all the status in the console window over there so you can see here it is trying to apply the code to the Azure app Services over there so it has been done successfully over there enough people could go ahead here the stating one done successfully so let's go ahead to the next step in the next step it has been queued now so now immediately as per The Continuous deployment it is start doing the deployment to the next slot that is here production one so please wait so you can see here it is now initialize that job downloading the artifacts now it is trying to define the code to the production slot over there so now it has been done successfully so we can look at here the production release pipeline so all the steps has been done here successfully in the production list pipeline now let me verify these changes so the Azure web app this is my production slot go to the overview section then here browse it so when I will browse it here you can see I'm getting here the deployment code over there and the same you will find out in the staging also because the code has been deployed in the sequence first it applied to the studying then it applied to the production one so this is the way how we implemented the cict for our asp.net core application using the Azure devops and using the Azure web apps over there now let's verify the complete cicd workflow which we have designed for our web app so let's open here the azure devops website over there and if you look at we already having a build pipeline where we added the continuous integration trigger so far we have only one uh build over here we don't have any other build because I have not done any change in my code and commit so as soon as I will commit the changes of my code it automatically initiate the build as per The Continuous integration trigger and as soon as it will finish the build artifacts over there suspect the release pipeline it automatically trigger my these pipelines over there so what I'm doing here I'm just going to remove this staging pipeline because right now we have to get two pipelines and both the pipelines we are doing the same thing so in the production we are also deploying the code to the staging then production so here is staging it's not required over here initially I have created it for testing purpose let me delete it here I'm just going to delete all the things which we have done from the stating let me remove it so if you look at here I'm having a end to end production list pipeline where we set up the deployment to the staging slot first and then we set up to the production one similar way we having a build pipeline where we just enable The Continuous indication now let's verify the complete workflow of the code so this is my code and what I'm doing here I'm just going to do here it change let me open here the home index.csstml and what I will do here I will do here a change welcome to azure devops cicd the using weapon so let's say using Azure web app so this is the change let's say I'm doing over here so let me go to the here the changes so there is option here in the right hand side for the git I mean here for so let's go to here the team Explorer and we just do check for the changes over there so go to the home and we having that changes over there you can see one file I just change over there let me let me see a change I'm doing here first time so it is update one then here from my select here commit all and push option I'm using here so in your video Studio you might get a different option so in my case I have updated my widget Studio 2019 latest version so that was just 2019 latest version they just updated the git experience or you can say the git tooling support they updated in the video Studio latest version of the 2019 so I'm just using here this one and the commit has been done so as per The Continuous integration trigger it should automatically initiate it as you look at its queued automatically as per The Continuous integration trigger so perfectly our CO3 that is working over there similar way it automatically initiate our release trigger as soon as it will complete over there so right now we will look at to the releases this is our releases so there is no lease over there because right now it is first building this one it has been done and after that it initiated our second release to the staging environment so this is the workflow which I shown in the picture now it is working so first we have done the with the build pipeline that we have been the staging now in our case it is a continuous deployment This One automatically to the build using the continuous integration trigger then to the staging then to the production one same it is happening over there so staging right now is doing when it would be succeeded it will proceed to the production one so now you can see here to the stating slot the build is succeeded you can see the release has been succeeded now let's go ahead how it is showing the output just go to the stating slot just browse it what are the new changes we have done we will see over here now you can see I'm getting here welcome to Azure devopcd using the Azure web app so perfectly we are getting the output over there as per this release and it has been succeeded to the production slot also let me access here the production slot also so this is my DNT web app dab box just go to the overview now let's verify the same changes to the production slot also so here also I'm cutting the same changes now so this is the way we just implemented here continuous integration and continuous deployment successfully in our asp.net core web application using the Azure web app

Channel: ScholarHat

Views: 35,026

Keywords: azure devops ci cd pipeline tutorial, azure pipelines tutorial, azure devops pipeline, azure pipelines, azure devops tutorial, ci/cd tutorial, devops pipelines, azure pipeline tutorial, azure devops build pipeline, azure devops pipeline tutorial, azure ci cd pipeline, ci/cd pipeline, ci/cd pipeline explained, how do you build a ci cd pipeline?, azure devops ci cd pipeline, creating a ci-cd pipline, ci/cd, azure devops, azure devops training, ci cd pipeline, scholarhat

Id: eOQL0nXQlLs

Length: 53min 54sec (3234 seconds)

Published: Wed Nov 30 2022