Azure DevOps Artifacts | Azure Artifacts In Azure DevOps | Using Azure DevOps Artifacts | Edureka

[Music] hey y'all this is taneshka from ideoreca and i welcome you all to this session so today we will be discussing on a new topic that is azure devops artifact before that make sure you subscribe to our edureka youtube channel and hit the bell icon to never miss any updates also if you are interested in any of the microsoft certification and training then do check out the links given below in the description so before we get started let's quickly have a glance on today's agenda so firstly we'll look on to what are azure devops artifacts followed by why do we use azure devops artifact and then we'll see the workflow of azure artifacts and lastly we'll have a demo on how artifacts work so with don't wait let's get started what are your artifacts so according to the definition azure artifact is a package management system integrated with azure devops that allows you to develop and share packages like maven npm and nugget etc via public and private feeds to any size business so basically azure artifacts is kind of an extension that makes it easy to discover install and publish packages in azure devops it's deeply integrated with other hubs like build so that package management can become a seamless part of your existing workflow it enables developers to share their code efficiently and manage all their packages from one place using azure devops artifacts developers can publish packages to their feeds and share it within the same team access organizations and even publicly so this was all about what are azure artifacts let's quickly move on to the next that is why azure devops artifacts so there are three main features in azure devops artifact which makes it more special and demanding so let's quickly have a look what are those three so first is you can keep your artifacts organized so what does it mean that you can share code effortlessly by storing any packages irrespective of whatever programming language you are using like maven npm nugget and python etc you can just feed them all together in the artifacts and keep it organized second is protect your packages so here it means that you can keep every public source package that you use including packages from npm.js and nugget.org save in your feed where only you can delete it and it is backed by the enterprise grade azure sls so that means that all your packages are safe and secure third is integrated package handling into your ci cd pipeline so what does it mean that you can access all your artifacts in builds and releases in which artifact integrates natively with the azure pipeline or ci cd2 so these were the three benefits or we can say features that makes azure devops artifacts more demanding and mostly helpful to users basically like developers so let's quickly move on ahead so next is azure artifacts workflow so let's see how azure artifact work so it is a three-step process in which makes it easy to work so like we can see the first step is to create a package so basically what is it a package feed is a location you use to host packages you want to deploy with a deployment manager so when you set up a deployment manager you need to choose a feed you want to use to host your package so here what do you do first you create a package feed or a team feed so once you create a team feed then we move on to the next step that is build integration so basically what do we do here is like we connect to the feed in the azure devops and then we start building integration the main purpose of build integration is to define the order in which the components and subsystem should be implemented which builds to create when integrating the system and how they are to be assessed after this we move on to the third step that is consumed from feed so here what do we do is that we pack and push packages to your feed and then we consume feed by running build and restoring packages from team food and setting up new solution locally to consume the field so these were the three easy steps or we can say the whole workflow of azure devops artifact so with no wait let's quickly move on to our demo where we'll see how do we work with the artifacts so first we need to open our terminal let's open our terminal and now what we'll do is we'll create a folder where we'll be storing our both the projects so let's quickly create the folder so here you can see our devops folder has been created now let's just confirm whether it has been created or no document all right so here you can see this is our devops folder so now here we'll be adding our both the projects whatever we'll be building so let's quickly build our projects let's move to our visual studio okay so here we will be creating our project so as i said i'll be using the java project so let's quickly make it ctrl shift p and this is the option create java project so just click on this and i'll be taking maven you can take any other tools like gradle spring boot corkers micro profile any of your choice for me i'll be choosing maven and then maybe not type quick start and our version would be 1.4 and now here we need to give a name to our group id so let's keep it as your rt but all right and now they ask for the artifact id so we'll keep it very simple project one and here we need to select the folder so we'll be selecting the devops folder which we had created so this would be our destination folder so here you can see it is executing all right so here you can see your group id artifact id and the version so our version would be 1.0 snapshot so just copy this and paste it over here hit enter and they ask for the confirmation of your properties so our group id is azure artifacts artifact id project 1 version 1.0 snapshot package so here we must update the package name it should be similar to the artifact id so let's just update it snapshot our version is 1.0 snapshot and package will name it as our artifact id so project one yes and here you can see our project one has been created successfully and here you get the message and we'll just open this all right so here as you can see this is project one and you do have your source files and pom.xml so this is the where you find all your dependencies so let's quickly build our project two will follow the same process ctrl shift p java project maven type 1.0 and our group id would be same so azure artifacts and this will name it as project 2. and select the folder destination folder all right so here we see our group id artifact id project 2 let's keep the version same so just copy this and we need to update our package so let's update it put to this all right so our project 2 has also been successfully built here you get the message we'll just open this as well so here also you can see your source file and your palm.xml file has been created so now both the projects are created now what do we need to do is to create the dependencies so let's create the dependencies for this we'll just maximize this in project 2 we'll come to this dependencies section and we'll copy this dependency code copy and just paste it below and now what do we do here is as we need to create the dependencies so we'll change the group id artifact id and your versions so what would be our group id is azure artifacts which we had created so let's just copy and paste and our artifact id is project one as we are making project one dependent on project two so let's write it project one all right our version would be 1.0 snapshot code and our scope would be system now below this we need to give the system path so let's quickly give the system path okay so our system path would be dollar base star like purchase 1 5 1 so here we get the option 1.0 snapshot.jar so we'll quickly save this and we'll open our terminal so let's open our terminal so now to build this jar file we need to go to project one so let's go to project one cb project one all right so here what do we do we'll just hit the command maven compile all right so here it shows it has been built successfully after this we'll just hit the command maven package all right so your wave in package command has also been run successfully let's quickly cross check it once let's go to project one now here we see the tab gate folder so let's quickly check so here here you can see your project 1.0 snapshot.js file has been created now what do we need to do is we need to copy this jar file and paste it in project two so for this let's create a folder in project two let's name it live and we'll copy this chart file and paste it in it ok now what do we do we'll run the same commands that is maven compile and maven package in project 2 as well so let's quickly go to project 2 may even compile all right so here you can see it has been built successfully let's run another command that is maven package all right so here you can see maven package has also run successfully so this is how you create the dependencies between the two projects now let's quickly move on to our azure we'll go to our azure devops okay so here first we'll be creating a project let's create a new project and let's name it alicia box and we'll make it private like you can choose any one of the like you can choose the visibility of your own choice so but i prefer private and we'll create it so this is our new project here you can see there are different options like boards reports pipelines test plans artifacts so first we'll go to pause and here we will be like uploading our project whatever we have created right now for this now what do we need to do the first step is like so let's go to our project now we have created the dependencies like we have created our java files and our both the projects are dependent on each other like so it is basically typically for like one developer environment but let us assume like if you have two different teams and then what you need to do that you need to always come over here and open the jar file and just update the versions of the jar file every time so what do you need is to have a central location where you have all these files and then every time whenever you compile these projects then it is going to go ahead and the latest file and then it is basically that you don't need any more like you won't have to just come over here and keep on updating your versions so it would be automatically done so for that what we'll do like we'll just delete this java files from here so that only the code is like transferred to our reports so let's go to our files and go to project one and in target there is a jar file so we'll just delete this chart file same would be done in project 2 project and we'll just delete this folder all right so now that is done so let's move on to our terminal now we need to like uh move to our destination folder where we have posted where we built our both the projects so i have come here to this devops folder now what we need to do is we need to send these projects these two projects into our git repository for that we hit in it and then and then comment so here you can see our both the files have been gone into the repository now what do we need to do is we will go to our repository and we just copy this get remote add origin so what do we need to do is we'll just copy this link copy and get remote add origin okay and conversion and now we'll use the git push command so let's use it get post i think you all right so our files are uploaded now just let's refresh this repository let's go to the first okay so here you can see why both the projects are uploaded over here so it has it is quite clean we just have our form x dot xml and our source folder we don't have our java files or anything as such now after this let's move on to our artifacts so here first is we need to create a feed so let's create a feed let's name it project as your app and here we can give the visibility it's upon you like whatever choice you need to give so you can give the visibility like only accessible to the members of the organization or to the specific people so i'll select the second option and end up streaming sources so here we like from the public sources we include the packages like no matter whatever languages you're using and our scope would be project it can be either project or organization so for me i'll be selecting the project and i'll just create it so yes as you can see here our feed has been created now next what do we need to do is connect to feed so here you can see all different languages uh the packages which you need to like connect and you need to feed on to the artifacts so here there are different languages like dot net nugget visual studio npm gradle python pip so you can choose any one of your choice for me i will be choosing maven as we have worked on maven so let's what do we need to do is here let's copy this repository and we need to paste it on to our project files so let's go to project 2 and let's search for our repository section so do we have any repositories so no we don't have repository we need to create a new repository so let's create a repository just below our dependencies so the false set for you please some close it all right now what do we do we will just paste the code over here and just save it now we can also copy this whole code and paste it on project one as well so this is a project one let's go and do the same thing under repository sorry under the dependencies replace this repository [Music] all right so now you can see this url so this url it needs some authentication as this is private so how do we give the authentication so let's move on to our azure devops here we'll go to personal access key tokens and here we'll be creating a new token so let's create a new token over here you can give any name to your token let's keep it object as your top app dot artifacts all right and let's give the authentication we'll give the packaging read write and manage once that is done let's create so as you can see your token is all created over here and this is your password all right so just copy this password now where do we put this keyword so that we can authenticate so there is a folder maven folder that is m2 dot m2 so we'll go to that m2 and here you can see the repository folder and there's a settings.xml so we'll go to the settings.xml file and here you can see this is the code where you can give the authentication to your maven project so here this is the code server under this you have your project id project azure.app and your username is your organization's name now let's paste the password which we had copied so let's paste it over here and let's save it so now let's go to our devops and we'll go to the artifacts connect to feed maven and so here you can see your settings.xml file your username is there and your personal access token which we created previously have been initiated now what do we need to do is copy this repository as it has been updated let's copy this and paste it again to our both the projects so we'll just copy this repository test it earlier and save it let's do this same with our project one so this is our project one already so we will save this as well now what do we need to do is we need to also have this distribution management code so let's find out if we have this section so we don't have it let's paste it again just below the repositories just close this copy paste now what do we need to do is copy the same repository code and paste it just inside this distribution management and save it all right now we'll just do the same thing with this is for the project one we'll do it for project two as well let's copy project two and paste all right so save it so now let's move on to the terminal of project one and deploy all right so here you can see it has been successfully built now let's just check whether it has come or no let's go back and refresh this so here you can see your project one artifact have been created just click on this and here you see all your details all your files are already existing now what do we need to do is just copy this dependency and we paste it in our projector so we'll just select this and paste it and save and that's [Music] deployed even this has been built successfully let's check refresh so here you can see our both the projects have been uploaded and this is how you push your packages into your artifacts i hope you all understood how actually the azure devops artifact works how do we push packages into our artifacts so this was all from my end thank you happy learning i hope you have enjoyed listening to this video please be kind enough to like it and you can comment any of your doubts and queries and we will reply them at the earliest do look out for more videos in our playlist and subscribe to edureka channel to learn more happy learning you

Channel: edureka!

Views: 16,346

Keywords: yt:cc=on, azuredevopsartifacts, azuredevopsartifactstutorial, azuredevopsartifactsmavenfeed, azuredevopsartifactsnuget, azuredevopsartifactsfeed, azuredevopsartifactsnpm, azuredevopsartifactspython, azuredevopsartefacts, azuredevopsartifactory, IntroductiontoDevOpsArtifact, azuredevopspublishartifacts, azure edureka, azure training, azure tutorial, edureka, azure devops, azure, azure artifacts tutorial, azure artifacts edureka

Id: o9OpFMQMSHw

Length: 25min 23sec (1523 seconds)

Published: Mon May 09 2022