In our last video we saw how we can make use of the bird pipeline with classical and with the camel.
And today we are going to be looking at even further the way that we can use to build a pipeline in
terms of the continuous integration and making use of the variables in the stuffs.
So if you remember in our previous videos we were using this bird configuration and the build platform
and all these variables within our artifacts that we created.
And again you can keep on adding any number of pipeline variables here and you can also define your
own variables.
And there are some predefined variables that you can see from here which is available in the document
like what are the different kinds of variables that you can use.
The one which we are using is the Asian Dodd bird directory which is nothing but this one.
The C column agent work and this is the exact same directory that we used while we're creating the UI
test pad and somebody that is a bird art artifact staging directory which is this one and the bird I.D.
numbers and you can see that there are so many different variables that you can use just the predefined
variables that you can use within your test build steps that you are using and similarly this triggers
is something very very important and this is where the Continuous Integration happens.
For instance if we enable this continuous integrations and if you're going to make any changes to the
master branch or all the branches you can do that as well.
So for instance if I'm going to change anything in the master branch then I'm going to trigger the build.
So this is where you can set this particular stuff.
And similarly if you want to scale you with the bird you can do that or you can also set up a build
trigger by for this Udemy course project once anything happens within this particular brand which is
nothing but the master branch so you can do that as well for the continuous integration and similarly
you can see there are some options where you can define the bare number from it.
So basically what our bill that we create right now has this particular format right now.
But you can change the bill format if you want.
You can give a description and also you can say that while the new bill that it cost is being processed
you can just enable it so that you can queue and start the new board in the available agent or the eligible
agent or you can just said this has passed so that it won't be executed are the bill on start at all.
And you can even disable this if you want and similarly you can automatically link this new work in
this particular bird and you can also include a wild card of the brand specification and if you're going
to view a status badge if you remember we discussed about this already you can do that as well.
So you can do all sort of jazz here in the options.
Similarly if you want to do retention you can do that retention as well.
So currently the retention has been streamlined but if you go into the product setting you can configure
that again.
It's kind of very very deep.
I don't really have to go into that yet but I'm going to go ahead and play around with it like how it
works.
Somebody can see the history of what has been happening for that particular build a pipeline that we
created.
So basically we just added this guy when he one time.
That's why there is only one history here that is not big history changes that we can see.
So I'm just gonna save this for now and I'm not going to be triggering any of the bird yet here so you
can see that the bird is currently not running at all but if I go to the files in my repo and currently
this is in the test branch but if I change this to maybe a master branch and if I am let's say gonna
go to the selenium test here and I'm just gonna hit the edit and I'm gonna make a field change here
and maybe I'm just gonna add a common Tier I'm just going to commit this change update or test one.
Which is fine.
And now once I go to the pipeline of the bird and if I go to the Udemy course project you can see that
the bird has been triggered just nothing but a CIA bird.
So basically this is not manual bird.
This is the continuous integration bird for or bird trigger that we have set.
So now you can see that it is automatically being triggered.
I did not did anything here manually rather once I made any changes to the master branch because that's
what we set in the bird trigger basically it automatically triggered the bird and it is running the
bird for us automatically.
So this is how we can see that we can set a trigger for the bird and we can see that the bird is automatically
executing for that particular trigger.
So this is what is the continuous integration of the bird which is happening within our eyes your pipeline.
So you're going to see that the board the repos and the pipelines and the pipelines within the pipeline.
The bird is all tightly integrated here guys.
It's all coupled together much cohesively so that it can do the execution for us without any monitoring
by us to perform these operations.
So everything is happening first of any problem.
And that's the power of the continuous integration and as you do up service starting our next video
we will see how we can make use of the release pipeline and we can create a new release here.
And also we will see how we can deploy the code in our local Internet Information Server and then we
can run the selenium test.
Also we'll understand the concept of the deployment groups how we can create the shared groups something
like this and then how we can run the tests across different machines and different groups are different
deployment groups in much efficient manner.