WEBVTT 00:00.240 --> 00:00.660 Hi guys. 00:00.660 --> 00:06.300 My name is Scott tech and I am from is it automation dot com and welcome to another section of our continuous 00:06.300 --> 00:11.820 integration development delivery with as your new course and in the section we are going to talk about 00:11.890 --> 00:18.450 as your artifacts and the section we are going to be coming to an end of this whole services which is 00:18.450 --> 00:25.890 offered by Microsoft as you do up services as your artifacts are your artifacts introduces the concept 00:25.920 --> 00:33.450 of multiple feeds that you can use to organize and control access to your packages if you are familiar 00:33.450 --> 00:42.180 with using packages from New get on r NPM jazz you can think of those places each as a single feed so 00:42.180 --> 00:47.070 you can use that single feed which is gonna be the one which you will be creating in this particular 00:47.070 --> 00:54.690 video and you are gonna be using the same feed for both the new get as well as for NPM jazz or even 00:54.930 --> 00:58.180 it can be a maven and things of that nature. 00:58.560 --> 01:05.390 So it's really helpful for companies to control the outside world packages and also track if any packages 01:05.460 --> 01:09.990 affected by any malicious code and also you can see that. 01:10.050 --> 01:16.440 What's the version everyone is using within the organization and control the uses of certain version. 01:16.440 --> 01:21.780 So the packages are one thing which the companies need to restrict their usage within the team because 01:21.780 --> 01:28.800 as you can see anybody with the access of internet within the team can straight away download any one 01:28.800 --> 01:34.050 of the new get packages are NPM days packages and they can install within their project and they can 01:34.050 --> 01:35.010 start using with it. 01:35.310 --> 01:42.090 But the problem is we're going to be using any packages which is not the one which you should be using 01:42.090 --> 01:47.400 for maybe there is some compatibility issues which the team has reported then probably you should wait 01:47.400 --> 01:50.320 for that compatibility should be resolved. 01:50.550 --> 01:55.470 But if you don't really have any control over that anybody can use any packages and you will end up 01:55.470 --> 02:01.030 with redoing all the babysitting works to resolve the issue which has already been identified with the 02:01.040 --> 02:02.000 new team. 02:02.010 --> 02:07.410 So these are your artifacts or something which are really helpful to track down what packages that you 02:07.410 --> 02:14.430 should be using and how you can control the usage of these packages from outside world so you can do 02:14.610 --> 02:20.130 many different things within the antivirus something that you can delete the complete package saws and 02:20.130 --> 02:25.800 then you can even reverse revert the retard package saws and you can use the latest version and things 02:25.800 --> 02:31.620 of that nature you can unlisted and you can re listed and then you can even promoted and things of that 02:31.620 --> 02:32.190 nature. 02:32.250 --> 02:35.430 So we'll be seeing everything in action and understand how things work. 02:35.430 --> 02:37.540 So stay tuned for our next video for it.