Azure DevOps - Create a simple Build Pipeline(CI) using Classic Editor

hello guys welcome back to our Channel my name is balram Prasad and I'm working with Microsoft as a senior software engineer in this demo we are going to see how we can create a build pipeline in Azure devops with classic editor for this demo let's go to visual studio in first we are going to clone a repository because we have already at existing repository called software's app demo and we can go to our user Branch we can see that all the details I am going to take that URL for this and I am going to paste that and then I am going to change that location where we can have that different project let's have the software's demo only name or we can put that software so this is going to now I am going to clone that now I am going to is my branch user branch and now inside user branch I want to add one project that will be asp.net code web app and let's put the same name for project also uh demo and you can print that one inside and we are going to create a new solution with all the details I am going to click on the next and then it will be dotnet 6.0 right now authentication type equals to none in configure for https so I am going to create is predicted now right now it is into folder view I want to change into solution export View and for project I am going to change that one little bit and say that CD remove let's run this locally first to see this is up and running now I'm going to push my changes to my local branch for that I am going to give changes going to select what files I'm going to push that way solve this files because that's not necessary so I am going to denote that file we can select that hey uh ignore this local item bin files or files Let's ignore that I want to check in my pages I want to ignore my properties launch settings and then not this look like them I want to do that CSS I want to do csi.js I do not want to do or leave in other things the state distribution jQuery is CS and other things so I'm not going so let's node this Let's ignore that WWE root itself because that I don't think is required all of that and now I'm going to select whatever we need stage that and then put in the thing initial commit is that and right now it is committed locally I am going to push to my branch now we have already this Branch so let's go and see that one if we fix that one we have just checking we can create a PR domain but before that one I want to sit up and see that how the build look like and build is being successful or not I am going to click on the setup build now we have multiple way to set up the pipeline and we can go because we have that four framework set up so we can go and select that core framework and we have multiple options to see that and dotnetcode.net code framework so right now what is our selection over there we can see that in more details that we have selected dotnet.net framework 6 I guess dot net framework.net6 note code so I'm going with it so we are going with this selection now asp.netcode.net framework and we can have Azure pipeline which will be yml pipeline which is going to build and then it is going to test we can have this way also and we can have different way right now this is yml way I am going to create with the classic way so I can go to pipeline in pipeline I can say that create Pipeline and in pipeline if we select this one yml way then if it will go to new way but let's go for classic editor now we have to select our repository which is our soft switch web app demo default Branch for manual incident build is mean and we can change that one when we are going to trigger so let's keep that and let's click on continue and if you have multiple team project then you can change the project to if you have multiple repository between the different way so you can change that whatever you want to do but for this demo because our code is in software's web app and demo we will go with that so next will be that which type of template you want to use you can have empty job you can select that whatever featured way we can have so let's go ahead and select asp.net because we know that our web app is asp.net core web app then we can use this template so I am going to click and apply it now we can change the name if you see the name is coming demo asp.net CI CI is continuous integration so let's change the name stop it demo and the next we can see that pipeline where it is going to run so this is going to run agent pool is your pipeline because we have not set up any hosted pipeline in other things so that you can get if you do not have any option to see this one you can raise the form so that you can get free grant from Microsoft to use Azure Pipeline and then we will see that which kind of job and other things are there all the person whatever details are there then first task yeah so it will install the new gate on that machine where the build is going to happen so this is 4.4.1 is quite old so I am going to change this one as a 6.1.0 and C6 point 1.0 at least and then next task is nuget restore where we have this whatever solution is inside our code it is going to pick that one see that where is the password package config or project.json depending upon project type then it is going to run nougat store command and right now the speed is we can see that feed or used nuget package packages from nougat.org this is different topic altogether when I will get some time we will see that on how to create a private repository from where it is going to detect get the package not from public one so we will see later the next option is that build where it is going to take the build solution file and building we can unlink this one right now it is for all solution if you have any scenario where if you have multiple solution and you want to build only one solution then you can unlink that one and if you unlink that then you can give the path whatever you can do you can browse the path and other things and you can keep that one so and this is the MS build argument what it is going to do and once package location it to whatever output is going to be it is going to put into build.r effect staging directory next is if you have any unit test and after build output if you need any test dot dll is there it is going to run that unit test using that all the test assembly meter so it is going to use Visual Studio test and run that and then it is going to publish symbol path and then finally it is going to publish that artifact which is the output from build staging directory to mean a drop location and this is what this uh build is going to do so let's go ahead and save this build and queue that so while we are going to queue we need to put the command and I am going to put the command that initial build and which Branch or tag we want to use so right now our code in into my usual Branch so I'm going to select that and then I am going to save and run now we can see that it is going to use this my user branch and this is that a change code change it is commit it is going to run so this was the last commit we did that and then it is going to run and it is going to display all the details for that and then we can see that what is happening by going into a gym job right now it is in slicing and once in a slicing is done it is going to do all the steps which we talked about right now to checking out all the code from our repository now it is going to install and see that if nugget is presented with that person or build a machine or not then you get restored from that package is it going to happen all the package whatever we are using into our solution it is going to restore all this then now it is building the solution and we have this uh surface demo dot Solutions it is going to build right now now it failed let's see it is saying that the future Global dietary is currently in preview let's go ahead and see if we have to update anything then build solution right now it says that Visual Studio latest so I'm going to select that Visual Studio 2022 and I will give a drive I can skip this comment and I can select my branch so let's see more changes and let's go what is the digital specification that is window 2019 let's see that I'm going to do windows latest there is no code inside main so it is not going to run anything so I am going to cancel this and then I'm going to one more time I am going to trigger that one so interesting so now it is working it was using the old version of EMS that is why it was not working so now if we see all of our task is succeeded and it is going to publish all the artifact and other things artifact it got published if you wanted to see artifact after the build and other things you can go into this place where it says that all the details whatever output is there this is the zip file which is output if you want to download and see that what is inside that one we can see all the dlls and other things will be there okay so once we download that one we can go ahead and see what are the different contents inside this one drop file is there and if we drill down we can see the output of all the bin files and other things will be present over there so if you see this application in all the settings on WW root and other things is going to come so this is how this build works if you are using classic and template if you want to create one more without template then if we go into use classic and then same thing we have to select and if we click on the continue we can go for either yml or either template in either we can go for empty job where all the settings will come let me select that latest version first in the pipeline and then we can change the name we can change the name from here also we do not have to go from that place so we can change that one and then we can add from this place so we can have different different complex things also if we wanted to have multiple agent settings and multiple steps we can do from classic editor also and we will see that one inside the yml also for that place also if you wanted to add any task in this agent job we can go ahead here and now we can find that one that hey I want to do no gate so what we want to go when we want to see that hey I want to install the nuget package so let's go ahead and see which version we want to do the six point in so we want to install now what we want to do so we want to do move it we store next step so let's go ahead and do that one nuget and command it is stored all the solution file we can select the solution file and other things from here by changing if you want to right now it my code is not mean it is not saying but I can go ahead and change this place web app test and if I go now it will browse my test place and we can see all the code where the software is demo and we can select that one individual solution is also going to build that way also we can do now we can go to next step and we can see that hey let's try to build up once because nougat is restored all this restored I can go and say that asp.net I want to build with asp.net task so let's try to find task so that will be Visual Studio build so I can go ahead and put that and this is the setting and then we have to put this all this manually that what is the build argument and other things so for time being I'm going back and copying that one inside that whatever pipeline it was generated that will be easy for me so I can copy paste all the details and it is the same details that what package it is going to do in other details so it all this I can mention here 2022 and then once we are done we can go ahead and say that if you wanted to taste then taste either you do not want to taste that one if you want to taste then you can run the test from Visual Studio test and you can add that test because right now we do not have any taste so we we are not going to do so this is basic steps and whatever additional step you want to add you can go ahead and add let's try to save this one and run that foreign so now it is building but after that one we did not added that drop locations if you go and see that in drop there is only consumed once there there is no publish so we can go ahead and change that to drop itself that lifts let me add publish artifact one so publish build artifact we have to do that and whatever is in from build a staging directory so drop it is going to do that one so let's save in queue one more time now we can see this publish is also completed and then we can go and see this is published it's coming and we can see in clock so for this video I just wanted to show you that how we can check in the code and how we can set up the build using classic editor for yml and other topic we will create another videos I hope this video will be useful if you are trying to create built-in pipelines thank you foreign [Music] foreign

Channel: SoftWiz Circle

Views: 3,553

Keywords: devops tutorial, azure devops pipeline tutorial, create build pipeline in azure devops, azure devops project, azure devops pipeline, devops tutorial for beginners, azure devops, create build pipeline using classic editor, azure devops ci cd pipeline, build pipeline using classic editor, classic editor for build pipeline, build pipeline classic editor, continuous integration, azure pipelines, build pipeline, build pipeline in azure devops, azure devops build pipeline

Id: 97XiIR2eGy0

Length: 18min 0sec (1080 seconds)

Published: Fri Apr 28 2023