Getting started with package management using Azure Artifacts

hi everyone I'm Henry Dixon lead p.m. with the azure devops artifacts team I'm here to help you get started with artifacts by introducing you to some of our features today I will help us walk us through the following scenarios first setting up a package feed to provide our teams with the ability to control our packages and their dependencies next I will then add attached my build pipeline to upload packages into our new team feed while also describing some of the benefits of having this feed finally I will show how to quickly consume packages from the feeds into a new solution let's go ahead and get started with the demo I've already created a project for my team and had transferred my code into a repository I've done a couple builds to verify that my code is ready however I do have some packages that I want my team to consume so I want to create a team feed so I can control our dependencies luckily for me as your artifacts is now installed by default and then I'll click on new feed input a new team name team feed and hit create this will create a feed for my team to use they can be assigned permissions to either consume from or contribute to the feed I'm going to leave the defaults for now which means that all product members can do both additionally I will leave the default upstream since to use packages publish to this feed and I'll touch on that a little more later I'll go ahead and create it now okay next I'm going to add the feed to my list of packaged sources so I'll click the connect to feed button or the tab in the header a pop-up is now shown that provides me the URLs that I need to continue since the package is I'm creating our new get I'm going to copy this first one and open up my development instance in Visual Studio now as I'm in Visual Studio I will go to my project the place where I need to go can be found under tools NuGet package manager managed to get packages for solution or I can right click on my solution and get there the same way from here I get a list of packages available from new georg the default feed for our new get packages however i want to ensure that my feed comes first and my team gets items from that feed so i click on the gear icon at the top right which opens up my package sources settings area since i'm adding a new source feed i will click on the plus sign and give it a name and then i will paste in the source information into the source field like so i will then remove this the the check mark for new georg because I want the feed to use as primary and I've enabled new get orgasm as an upstream which I'll touch on later once I do this I am good to go ok the next step is to run a build and place a package in that feed therefore I can come back to my build pipeline and add new yet tasks to push the packages into the feed this will help update the packages in the team feed as time goes on I now go back to the azure DevOps and click on the Edit two of the build pipeline that I want to change again I'm adding a task so I hit the plus sign to find a task to add to my build I searched for new get and pick the first new get task since I'm pushing new NuGet packages I want to move it to a place after my build processes then I switched the command to push and then I update the target feed to the feed I've created for my team to validate that this works I can either save and queue or since I have CI configured on this pipeline I can wait until I check in a code change since I'm eager to validate this for my team I will choose save and queue this goes ahead and kicks off a build that I can then see the progress of while the build is running I want to tell of the reasons why I'm creating a team feed or even a set of feeds is a good thing many of you may be content with just using the default public sources of nougat or NPM feeds at nougat org or NPM j/s comm respectively these are great and we have listed them in our feeds as public upstream sources or public packaged providers without upstreams if the public site endpoints are interrupted for any reason DDoS other issues your build will have problems compiling until the public site returns to functionality another example is much more interesting two years ago a popular package was a low-level dependency for many packages and use today the package owner pulled that package causing upstream issues for packages listing it as a dependency thousands of packages and thousands of builds were impacted by this in both of these cases feeds with up streams enables help developers maintain productivity a feed will not only host a package you create but also the dependent packages from the public upstream and stored as a saved copy so while the second incident caused quite a bit of problem for developers teams using feeds with up streams enable would still be able to use their packages since the removed package would still be resident in the team's feed ok let's go ahead and check on my bill I believe it's complete okay it looks like my build is complete so I should be able to go and see the artifacts now within the team feet and yes it looks like the artifacts were just published into the team feet great so what we're going to do now is we're going to consume a package one of these new packages from another solution so I'll go back to visual studio and change to a different solution so now that I've changed to a different solution open it up in the solution Explorer and again I can get there from tools NuGet package manager manage packages for solution but since I've already been there before I'll go ahead and right-click and manage my new get packages now I see that in the new get package manager I have the ones that are installed but I can now browse select the package source and select my team feed now from here I now see the new team feed packages that are available to me to install I just need to install my Dixon look and listen I click on the install and it now comes back into my solution for me to go ahead and go thanks for watching this introductory video we hope this helps you get up to speed with producing and consuming packages and creating package feeds for your teams while this video targeted NuGet we have a ton of information around NPM Gradle and maven packages with more protocols being on-boarded all the time please feel free to ask myself for my team questions on twitter go the Azure DevOps website for more information or look us up on your UserVoice package management I'm Henri Dixon with the Azure DevOps artifacts team happy coding

Channel: Microsoft Visual Studio

Views: 48,862

Keywords: Azure, DevOps, Azure Artifacts, npm, maven, package management

Id: b3BPkyikvNM

Length: 8min 6sec (486 seconds)

Published: Mon Sep 10 2018