WEBVTT 00:00.450 --> 00:07.270 Until our last video we saw how we can create a build pipeline with the help of the Yemen files. 00:07.350 --> 00:13.560 And today we are going to be working with the same build pipeline but using the classical editor which 00:13.560 --> 00:19.890 is something that you can see while creating this particular build pipeline you will ask you to choose 00:20.400 --> 00:22.590 the user of the classical editor. 00:22.620 --> 00:25.960 So this is the classic there which you might have seen in the past. 00:25.970 --> 00:26.300 Yes. 00:26.310 --> 00:29.260 Which is nothing but the visual studio team service. 00:29.340 --> 00:32.190 And even if you have a small studio team Foundation. 00:32.190 --> 00:35.630 So 2018 or 2017 you can see this. 00:35.640 --> 00:37.370 It's exactly the same thing. 00:37.380 --> 00:43.070 So this time I'm going to do exactly the same thing as I want to choose this particular as your rep. 00:43.080 --> 00:46.510 Get from here for this particular repository. 00:46.560 --> 00:52.470 I want to continue and you can see that the template is a little bit different as we saw in the slide. 00:52.470 --> 00:58.770 So basically I'm just going to choose a A.S.A.P. darknet core which is pretty much exactly the one which 00:58.770 --> 01:01.080 we used in the Yamana file as well. 01:01.080 --> 01:07.680 And then once I hit apply you can see that this particular window is a little bit different than from 01:07.680 --> 01:13.980 before it is even more UI based than the one which has the editor. 01:14.280 --> 01:19.560 And you can see that it will ask you for the pipeline which doesn't prove that you're gonna be using. 01:19.650 --> 01:25.260 So you can say I'm going to use that Udemy pool which is pretty straight forward and easier and then 01:25.800 --> 01:28.200 you can also specify that test if you want. 01:28.200 --> 01:29.940 And then there is this publish. 01:30.090 --> 01:33.230 And if you want to do a copy files you can do that as well. 01:33.240 --> 01:40.830 For instance if I'm just going to hit the plus symbol and if I just search for copy and then you can 01:40.830 --> 01:43.570 see there's this copy file so I can add. 01:43.590 --> 01:46.250 So this way this copy file comes in here. 01:46.290 --> 01:51.180 You might have been familiar with this as of now because this is exactly the same thing that we did 01:51.210 --> 01:52.090 even before. 01:52.470 --> 02:01.380 So the did the source file for the selenium this one and the target file is going to be the artifact 02:01.380 --> 02:03.980 files for the user test which is this one. 02:04.050 --> 02:04.660 Right. 02:04.680 --> 02:06.720 So we did exactly the same thing. 02:06.720 --> 02:12.480 And you can even see the same thing with the Yamana file that we used in our previous video. 02:12.570 --> 02:14.610 So you can do that as well. 02:14.610 --> 02:15.600 That's a kind of cheat. 02:15.660 --> 02:22.910 If you don't really know what is the syntax you can actually copy from here if you want and the artifact 02:22.910 --> 02:24.900 name is a drop which is fine. 02:24.920 --> 02:32.840 So I'm just gonna to to save and Q So you can see that it's going to ask me whether I'm gonna be saving 02:32.840 --> 02:37.340 this I'm just gonna saving it and the build piping has been created. 02:37.340 --> 02:43.610 And once you go to the bird you can see that the agent is kind of configured and now it is running the 02:43.610 --> 02:49.790 whole boot process for us it is pretty much exactly the same like how we did in our previous video just 02:49.790 --> 02:58.400 that instead of using the older way we just nothing but the normal file we are using the classical editor 02:58.640 --> 03:00.050 to run the process. 03:00.080 --> 03:07.400 So this way we can see that we can use the exact same process of building or application with both the 03:07.400 --> 03:13.270 classical editor and with the Jamil file and then we can also see how things are actually working. 03:13.340 --> 03:16.280 So you can see it is also doing the exact same thing. 03:16.300 --> 03:21.610 I can go to the summary and you can see that it also shows you the whole changes here. 03:21.890 --> 03:29.900 So you can see it's executing that and let's wait for the artifact to be published so that I can show 03:29.900 --> 03:33.080 you the drop file in the summary. 03:33.080 --> 03:37.700 If I select this particular build pipeline you can see that it has been completed successfully. 03:37.790 --> 03:45.390 So this is how we can work with the classical editor of the build pipelines in our next video. 03:45.390 --> 03:54.030 We'll also see how we can actually use something called as variables and triggers and also some of the 03:54.030 --> 04:00.990 options which is available here within the bird and also the retention policies and history of the builds 04:01.080 --> 04:02.540 in our next video. 04:02.550 --> 04:02.970 Thank you.