Until our last video we saw how we can create a build pipeline with the help of the Yemen files.
And today we are going to be working with the same build pipeline but using the classical editor which
is something that you can see while creating this particular build pipeline you will ask you to choose
the user of the classical editor.
So this is the classic there which you might have seen in the past.
Yes.
Which is nothing but the visual studio team service.
And even if you have a small studio team Foundation.
So 2018 or 2017 you can see this.
It's exactly the same thing.
So this time I'm going to do exactly the same thing as I want to choose this particular as your rep.
Get from here for this particular repository.
I want to continue and you can see that the template is a little bit different as we saw in the slide.
So basically I'm just going to choose a A.S.A.P. darknet core which is pretty much exactly the one which
we used in the Yamana file as well.
And then once I hit apply you can see that this particular window is a little bit different than from
before it is even more UI based than the one which has the editor.
And you can see that it will ask you for the pipeline which doesn't prove that you're gonna be using.
So you can say I'm going to use that Udemy pool which is pretty straight forward and easier and then
you can also specify that test if you want.
And then there is this publish.
And if you want to do a copy files you can do that as well.
For instance if I'm just going to hit the plus symbol and if I just search for copy and then you can
see there's this copy file so I can add.
So this way this copy file comes in here.
You might have been familiar with this as of now because this is exactly the same thing that we did
even before.
So the did the source file for the selenium this one and the target file is going to be the artifact
files for the user test which is this one.
Right.
So we did exactly the same thing.
And you can even see the same thing with the Yamana file that we used in our previous video.
So you can do that as well.
That's a kind of cheat.
If you don't really know what is the syntax you can actually copy from here if you want and the artifact
name is a drop which is fine.
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
this I'm just gonna saving it and the build piping has been created.
And once you go to the bird you can see that the agent is kind of configured and now it is running the
whole boot process for us it is pretty much exactly the same like how we did in our previous video just
that instead of using the older way we just nothing but the normal file we are using the classical editor
to run the process.
So this way we can see that we can use the exact same process of building or application with both the
classical editor and with the Jamil file and then we can also see how things are actually working.
So you can see it is also doing the exact same thing.
I can go to the summary and you can see that it also shows you the whole changes here.
So you can see it's executing that and let's wait for the artifact to be published so that I can show
you the drop file in the summary.
If I select this particular build pipeline you can see that it has been completed successfully.
So this is how we can work with the classical editor of the build pipelines in our next video.
We'll also see how we can actually use something called as variables and triggers and also some of the
options which is available here within the bird and also the retention policies and history of the builds
in our next video.
Thank you.