WEBVTT 00:00.300 --> 00:07.210 In our last video we saw how we can make use of the bird pipeline with classical and with the camel. 00:07.410 --> 00:14.430 And today we are going to be looking at even further the way that we can use to build a pipeline in 00:14.430 --> 00:19.120 terms of the continuous integration and making use of the variables in the stuffs. 00:19.140 --> 00:25.890 So if you remember in our previous videos we were using this bird configuration and the build platform 00:26.370 --> 00:31.120 and all these variables within our artifacts that we created. 00:31.200 --> 00:37.290 And again you can keep on adding any number of pipeline variables here and you can also define your 00:37.290 --> 00:38.460 own variables. 00:38.460 --> 00:43.620 And there are some predefined variables that you can see from here which is available in the document 00:43.680 --> 00:46.390 like what are the different kinds of variables that you can use. 00:46.530 --> 00:51.630 The one which we are using is the Asian Dodd bird directory which is nothing but this one. 00:51.660 --> 00:58.230 The C column agent work and this is the exact same directory that we used while we're creating the UI 00:58.230 --> 01:05.310 test pad and somebody that is a bird art artifact staging directory which is this one and the bird I.D. 01:05.640 --> 01:11.340 numbers and you can see that there are so many different variables that you can use just the predefined 01:11.380 --> 01:18.530 variables that you can use within your test build steps that you are using and similarly this triggers 01:18.530 --> 01:23.460 is something very very important and this is where the Continuous Integration happens. 01:23.460 --> 01:29.400 For instance if we enable this continuous integrations and if you're going to make any changes to the 01:29.400 --> 01:33.480 master branch or all the branches you can do that as well. 01:33.480 --> 01:38.930 So for instance if I'm going to change anything in the master branch then I'm going to trigger the build. 01:38.940 --> 01:41.460 So this is where you can set this particular stuff. 01:41.940 --> 01:47.190 And similarly if you want to scale you with the bird you can do that or you can also set up a build 01:47.190 --> 01:55.910 trigger by for this Udemy course project once anything happens within this particular brand which is 01:55.920 --> 02:03.080 nothing but the master branch so you can do that as well for the continuous integration and similarly 02:03.290 --> 02:07.130 you can see there are some options where you can define the bare number from it. 02:07.160 --> 02:11.030 So basically what our bill that we create right now has this particular format right now. 02:11.420 --> 02:13.850 But you can change the bill format if you want. 02:13.850 --> 02:19.610 You can give a description and also you can say that while the new bill that it cost is being processed 02:19.640 --> 02:25.220 you can just enable it so that you can queue and start the new board in the available agent or the eligible 02:25.320 --> 02:32.310 agent or you can just said this has passed so that it won't be executed are the bill on start at all. 02:32.420 --> 02:37.670 And you can even disable this if you want and similarly you can automatically link this new work in 02:37.670 --> 02:44.420 this particular bird and you can also include a wild card of the brand specification and if you're going 02:44.420 --> 02:49.550 to view a status badge if you remember we discussed about this already you can do that as well. 02:49.640 --> 02:53.530 So you can do all sort of jazz here in the options. 02:53.600 --> 02:58.310 Similarly if you want to do retention you can do that retention as well. 02:58.310 --> 03:05.630 So currently the retention has been streamlined but if you go into the product setting you can configure 03:05.630 --> 03:06.730 that again. 03:06.800 --> 03:07.900 It's kind of very very deep. 03:07.910 --> 03:12.290 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 03:12.290 --> 03:12.970 works. 03:13.010 --> 03:18.740 Somebody can see the history of what has been happening for that particular build a pipeline that we 03:18.740 --> 03:19.100 created. 03:19.160 --> 03:21.890 So basically we just added this guy when he one time. 03:21.920 --> 03:27.630 That's why there is only one history here that is not big history changes that we can see. 03:27.680 --> 03:34.280 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 03:34.280 --> 03:41.570 can see that the bird is currently not running at all but if I go to the files in my repo and currently 03:41.600 --> 03:50.590 this is in the test branch but if I change this to maybe a master branch and if I am let's say gonna 03:50.600 --> 03:57.380 go to the selenium test here and I'm just gonna hit the edit and I'm gonna make a field change here 03:57.380 --> 04:02.890 and maybe I'm just gonna add a common Tier I'm just going to commit this change update or test one. 04:02.930 --> 04:04.050 Which is fine. 04:04.140 --> 04:10.850 And now once I go to the pipeline of the bird and if I go to the Udemy course project you can see that 04:10.850 --> 04:14.000 the bird has been triggered just nothing but a CIA bird. 04:14.000 --> 04:16.460 So basically this is not manual bird. 04:16.460 --> 04:21.680 This is the continuous integration bird for or bird trigger that we have set. 04:21.680 --> 04:24.530 So now you can see that it is automatically being triggered. 04:24.530 --> 04:29.990 I did not did anything here manually rather once I made any changes to the master branch because that's 04:29.990 --> 04:34.880 what we set in the bird trigger basically it automatically triggered the bird and it is running the 04:34.880 --> 04:36.510 bird for us automatically. 04:36.530 --> 04:43.670 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 04:43.910 --> 04:46.700 executing for that particular trigger. 04:46.760 --> 04:53.750 So this is what is the continuous integration of the bird which is happening within our eyes your pipeline. 04:53.870 --> 04:59.480 So you're going to see that the board the repos and the pipelines and the pipelines within the pipeline. 04:59.480 --> 05:02.700 The bird is all tightly integrated here guys. 05:02.710 --> 05:10.580 It's all coupled together much cohesively so that it can do the execution for us without any monitoring 05:10.580 --> 05:12.590 by us to perform these operations. 05:12.620 --> 05:15.080 So everything is happening first of any problem. 05:15.080 --> 05:20.450 And that's the power of the continuous integration and as you do up service starting our next video 05:20.670 --> 05:26.090 we will see how we can make use of the release pipeline and we can create a new release here. 05:26.090 --> 05:33.290 And also we will see how we can deploy the code in our local Internet Information Server and then we 05:33.290 --> 05:34.690 can run the selenium test. 05:34.790 --> 05:40.370 Also we'll understand the concept of the deployment groups how we can create the shared groups something 05:40.370 --> 05:47.300 like this and then how we can run the tests across different machines and different groups are different 05:47.300 --> 05:49.520 deployment groups in much efficient manner.