Continuous Integration with Maven, Jenkins,Git & GitHub part-1

Continuous Integration with Maven, Jenkins,Git & GitHub part-1


Continuous Integration with Maven, Jenkins,Git & GitHub part-1

Topic :
1. Continuous Integration with Maven
2. Jenkins
3. Git \u0026 GitHub

#git #github #jenkins

-------------------------------------------------------------------------------------------------
Udemy Courses:
---------------------------------------------------------------------------------------------------
Manual Testing+Agile with Jira Tool
https://bit.ly/3EGoWpE

Selenium with Java+Cucumber
https://bit.ly/3Fc64R1

Selenium with Python \u0026 PyTest
https://bit.ly/3udHyZ6

Selenium with python using Robot framework
https://bit.ly/3ENgIfk

API Testing(Postman, RestAssured \u0026 SoapUI)
https://bit.ly/3OLD4Tl

Web Automation using Cypress with Javascript
https://bit.ly/3AT9Z2e

Jmeter-Performance Testing
https://bit.ly/3ubT7QN

SDET Essencials(Full Stack QA)
https://bit.ly/3GTRK0w

Appium-Mobile Automation Testing
https://bit.ly/3F9D6kp

Java Collections
https://bit.ly/3VhcljS

Java Programming
https://bit.ly/3VDlXVF

Cucumber BDD Framework
https://bit.ly/3F7d69r

Protractor with Javascript
https://bit.ly/3FcG6Ng


Content

0.06 -> so in the last decision till last session how we  have seen how we can implement our framework from  
7.02 -> the scratch so as part of the implementation  right so we have seen different things like  
12.54 -> starting from maven project updated formed an  XML and we have created the folder structure  
19.02 -> and then we automated three test cases one is a  simple login then login data even test case and  
25.05 -> then adding it new to new customer test case  so along with this these three test cases I  
30.21 -> will also provide you another three test cases  which is already automated just you can import  
36.81 -> those test cases in your Eclipse project and you  can try them and if you want to try yourself we  
41.91 -> can also try them so I will provide you those  two test case implementation part ok now once  
47.82 -> we have done the phase one so the next phase of  framework is execution part ok this is also very  
53.7 -> very important so execution and then we have a  maintenance these are all three different phases  
59.43 -> we discussed so execution and maintenance will  be part of continuous integration so from today  
65.43 -> and tomorrow topics are very very important so  please focus on this and I am going to cover  
70.41 -> most real-time top real-time concepts exactly  what will happen in the projects like how the  
76.05 -> developer tester and DevOps team will communicate  each other so all these things will be covered  
82.05 -> and today's in tomorrow session so execution and  maintenance so these are the two different phases  
87.63 -> comes under continuous integration so here we need  to understand what is the continuous integration  
93.84 -> so continuous integration is a process where the  QA or developer and DevOps so these three teams  
102.45 -> collectively working together towards achieve a  one-goal okay there is a continuous integration  
107.79 -> process so continuous integration is a basically a  process okay where everything will happen Valerie  
114.48 -> so from once a developer will happen development  will happen the other side testing will happen and  
119.28 -> the other side testing and development integration  will happen so all these things will continuously  
124.05 -> happen and everything is dependent okay so  the entire process is called as a continuous  
130.11 -> integration process so we are also going to  discuss today that one and so execution pattern as  
137.28 -> part of execution so we need to know how many ways  we can execute our test case so once I started  
143.52 -> thinking so I will talk about what is continuous  integration in detail so before that we need to do  
149.19 -> a few more things here how many ways we can exceed  our test cases so far how we have executed our  
156.69 -> test cases using destiny dot XML is a main side so  using destined in dot XML so we have added all our  
163.5 -> test cases and then have executed test engine dot  XML so within the Eclipse within the Eclipse is  
170.37 -> wanting the YouTuber test cases we use destiny dot  except fine but there is also another way we can  
176.28 -> also execute over all test cases or test so using  formed at except men so so far we have used for  
181.68 -> medics ml for only one purpose so that is we just  added all the dependencies and it is automatically  
188.31 -> downloaded all the jars and attach them to your  project so that's the only one you say we have  
193.14 -> seen so far right but now onwards we are going  to see few more uses of palm-reading symbol so  
199.77 -> ii uses of bounded xml is we can also run all the  test cases everything whatever we specified in the  
206.7 -> test and you don't XML but again bounded XML also  will internal legs you could test and you wrote  
212.58 -> XML okay but if you have a testing it at XML file  why we need to again in school through power XML  
219.57 -> file 5 it is required because destiny dot XML file  can be executed only within the Eclipse so outside  
226.89 -> of the Eclipse if I close my Eclipse without  your having eclipse we cannot exhibit XML file  
231.69 -> so Eclipse is mandatory required but when I run  my test cases using bomb detection well we don't  
237.75 -> require any Eclipse even without eclipse also  we can run about automation test cases ok that  
243.3 -> is another benefit from on with XML but before  executing format xml without eclipse first it  
250.08 -> should able to execute within eclipse everything  should be successful within eclipse and if format  
255.51 -> XML is able things go to successfully bdh and  then we can execute all the test cases without  
262.27 -> eclipse okay so palm read examples the first four  approaches run the test cases with me Minh bombed  
270.01 -> at XML within your eclipse the second approach  is run test cases through May 1 zln so here we  
278.8 -> don't require a clip so run the test cases through  me one CLI command line interface we can run it  
283.75 -> without having any eclipse the third approach is  we can run the test cases using Thunderbird file  
289.72 -> we can just create one file and bad file and  if you just one with single click we can run  
295.72 -> all your test cases and the last fourth one is  a run test cases using Gigi so this is again a  
301.78 -> step by step process we cannot directly jump into  the fourth stage so it is a step by step so first  
308.14 -> we should able to run our test cases for Matic  Sigma if it is successful then we can execute  
313.63 -> our test cases through command prompt even the  first phase is not successful we cannot go for  
318.31 -> the second phase these are all basically phases ok  one two three four phases but ultimate goal is we  
323.56 -> should able to exhibit our test cases through  Jenkins so this will happen every time in the  
328.42 -> real-time environment ok so first time first row  in the first phase we will execute our test cases  
334.84 -> using quadratic sample maven format xml and the  second phase once it is successful then in the  
340.84 -> second phase we execute through command prompt  and here we will close dumpling links if you  
345.28 -> don't require eclipse and then the third phase we  will execute through London bad file and if you  
351.16 -> want to run your test cases to run that bad file  first of all it should run through command prompt  
356.59 -> and successful and finally front out bad fellows  successful and then we will go endings with the  
362.14 -> same test cases in Jakob's so in the Jenkins  itself we will run for under bad fan ok these  
368.62 -> are the different four phases we have or we can  execute our test cases now continuous integration  
374.5 -> will start from the Jenkins here I will talk about  more on continuous integration so first let us  
380.35 -> focus on first three items so first one is how to  run the test cases with maven or not XML so to do  
387.88 -> this what we have to do is go to your Eclipse now  open politics mmm so in the in your palm read XML  
395.98 -> you don't see this particular thing so this is  newly added so currently work on dot XML will be  
402.1 -> like this this is your boundary example all right  so this is your format xml so in the palm - takes  
409.36 -> ml what you guys can do is we along with these  dependencies we need to also add other type of  
415.6 -> increase called plugins so we need to add two  types of plankings so to execute our test cases  
422.92 -> through poundin expounded xml file so what are  those plugins the first approach I'm writing here  
429.88 -> run the test case is using format XML within your  Eclipse so if you want to run this we have to add  
436.63 -> these two plugins one is maven compiler plugin  may one show fire plugin so these are the two  
444.01 -> plugin these are also just like a dependencies  it is also an increase so we can add these two  
449.53 -> dependencies in the format XML file so where we  have to add how we have to add so very open your  
456.64 -> Eclipse after completion of this properties time  and before starting the dependencies here we need  
464.62 -> to add so before adding this before adding this  we need to first write a builder tag okay in the  
472.18 -> build attack this is a manual entry we have to  buy in the builder time we have to add one more  
477.43 -> tag called plugins plugins so inside this luggage  we need to add those two plugins the first plug-in  
485.47 -> will be this one so this is the first plug-in  entry this is May one compiler plug-in so this  
492.61 -> plug-in is responsible for compile your XML files  and test case everything so if you want to compile  
499 -> something you need to use this particular project  this is one thing and the other plug-in is also  
504.01 -> there that is called show file plug-in should  find cracking this is another plug-in so under  
511.36 -> build attack under plugins time we need to add two  blank it is the first one and this is the test one  
517.51 -> and the second second plug-in is responsible for  execution of your test in G dot X and the first  
524.65 -> one is responsible for filing all the code if  there are any issues it will show you and the  
529.57 -> second mechanism actually responsible for running  your ex and my fastest indeed not xml file okay  
536.02 -> within your project so these are the two different  these are the additional interests which we need  
541.06 -> to add in your partner XML in addition okay so  now we have added this plugins once you have  
549.13 -> added this plug-in so what your dependencies  should be still there okay these are the only  
553.54 -> additional plugins which we need to add so I will  just send you these two plugins you can just add  
558.31 -> in two palm block your four hundred XML you can  do that so once we have saved this particular  
562.51 -> file and once you save these entries after that  just update your project so as soon as we have  
569.26 -> added this plugins to plugins just right click  on your project go to main one and here you can  
576.19 -> see one option called update project ok so just  click on this update project now it will show you  
582.73 -> the project name select and click on OK button  so it will try it in to update all the project  
588.19 -> and if there are any dependencies everything  in any files are missing configuration files  
592.15 -> are missing it will automatically download and  keep it everything ready so the first time now  
597.94 -> soon as we have added these two plugins you need  to just right-click and just update your project  
604.15 -> right-click may 1 and update project so this is  option you have to select ok so once I have done  
610.96 -> this setting now we can run the format XML and  automatically internally that test cases will be  
616.66 -> executed now the first important thing is when  you run your desk case is using format xml you  
624.04 -> will get this in error first time in your eclipse  in your eclipse you will see this kind of error no  
629.86 -> compiler is provided in this environment perhaps  you are running on JRE rather than JDK so this  
637.15 -> is a error you will get at the first time when  you run your format xml file so the solution for  
642.55 -> this is why you are getting this one is because  maven is required jdk not JRE but so for whatever  
649.54 -> is configured everything is running on junior  so if you go and see your windows preferences  
654.79 -> and here currently by default e in your eclipse  all your eclipses this option will be there you  
663.25 -> don't see this JDK option okay you will see this  option so when I use this default option just I'm  
669.16 -> just shifting this option now when I run this  bounded XML file it will throw some ever let me  
674.11 -> just executed see what ever it will do run as  may one test so this is how we need to execute  
679.99 -> your comrade XML so here you can just run as  a word test this is the one we can do or we  
686.11 -> can also write Li here run as run as maven test  so this is an option you guys should be used ok  
692.77 -> because we are running the pomade XML from maven  so when I run this my code will throw some error  
699.04 -> so may 1 test now can observe yes clearly so now  we can see these are the different episode would  
706.33 -> still not it started yeah I think it is executing  but because I already added that one so it is not  
713.68 -> giving anything so it is started execution without  any issue but in your case you will definitely get  
720.07 -> one issue first and so that is this one and test  cases are running successfully and in your case  
726.43 -> you will get this error in the command window  so what you guys can do is just go to window  
731.38 -> preferences and here the JRE is there right so I  have to remove this actually I haven't removed but  
738.61 -> in your case what you guys can do is just go to  add here ok so give go to add and standard VM next  
746.08 -> and here just browse your JDK path just browse  your JD Kiba that's more important ok let me just  
754.54 -> read no and show you just to hold up ok my test  case is done so far now what I can do is I just  
761.38 -> remove my option and show you what is the neighbor  so JDK is already there so I'm just removing this  
766.78 -> my JDK but now so for your is this will be the  current situation okay so JR will be selected  
772.54 -> and apply apply and close now again one more time  and running my palm read XML unmask maven test
785.65 -> okay so it is again running but first time and  you see this particular angry so you guys should  
790.99 -> update the JDK okay and later you can just remove  it still it is working because it is trying to  
797.35 -> download something from the JDK so that is more  important so still it is running perfectly right  
802.81 -> my test cases are running right now you can see  the first test case is done now in a second test  
809.65 -> case but you will definitely get this error  first time okay so the solution for this is  
815.98 -> you need to go to window references and here let  it be here and click on add standard VM next and  
823.99 -> here go to directory and JDK is they write so  JDK wherever the Java is installed select the  
830.71 -> JDK then select the folder so automatically it  will get the JRE name and everything then just  
837.31 -> click on the finish now we will see these two  entries okay so now the select the first one  
842.35 -> and then applying close so this is a solution you  have to apply if you are getting this particular  
848.32 -> error okay done so my test case have been executed  through comrade XML file so let me and currently  
856.27 -> all my test cases I have enable in the XML file  currently two test cases have been enabled data  
861.61 -> driven dust I have just commented and rest of  the two disc cases I have a name now one more  
867.76 -> time I am executing format xml run as a word test  so once we have run the Mima test it will start  
876.34 -> execution of your test cases here and still you  can see the screen and UI so every time you do  
887.44 -> some changes we have to update your maven project  until unless you update your project it will not  
892.27 -> take the changes latest changes so largely  is done it is trying to add a new customer
897.67 -> login is successful so now I think it is  trying to add in customer ok now it is  
911.71 -> clicking on customer every time it the email it  is providing a dummy data so the customer knows
919.59 -> okay so we're done so my desk case is completed  fine so through bounded XML we are able to take  
925.38 -> successful xvideo test cases so this is how  we need to do the first thing is in the format  
930.15 -> xml we need to add these two entries there  is the first thing you have to do and then  
934.68 -> we have to use these references go to window of  preferences hearing stop gr you have to add jdk  
939.72 -> path then apply in close after that execute your  contradicts okay so this is very very simple so  
947.31 -> once you have successfully executed bounded  xml file in your eclipse then the next step  
952.68 -> is we can go and execute your test cases through  command prompt without having any eclipse run the  
960.87 -> test cases using command prompt without having  eclipse or without using eclipse so here how it  
966.87 -> is possible is we have to install complete maven  software so normally the maven is available in  
974.07 -> two different flavors maven is available in two  different flavors so in the same a one one is it  
981.24 -> is available as eclipse plugin it is available  as eclipse plugin so just we have already have  
988.95 -> the maven plug-in within eclipse so by using that  particular plugin still we are able to create the  
994.41 -> Maven project for XML file updated so all these  things we have done because we have already have  
999.78 -> the Eclipse plug-in within the Eclipse we are  able to do that but if you want to run my test  
1005.33 -> cases or if you want to run my bounded xml through  command prompt right so we need to install may 1  
1012.74 -> on operating system so maven is available as an  installer on specific operating system so we can  
1019.43 -> install complete maven software on Windows Linux  or UNIX or in your drafting system so may 1 is a  
1026.36 -> software which is available as two flavors one  is it is available as a Eclipse plugin and is  
1032.45 -> also available as a complete installer on specific  operating system so if you want to run this maven  
1038.39 -> or if you want to use this feature to come across  we have to completely install me one so you have  
1044.99 -> to download maven softer and you have to install  this right and this is very very simple I will do  
1050.18 -> I'll show you how we can do this so to download  this maven software on Windows we need to just  
1057.56 -> go to Google and just type download a once-off  it just type download need one for bring those
1067.25 -> so once you open this particular link you will  see download Apache maven this is also Apache  
1076.04 -> foundation from Apache foundation just click on  this first link now it will go to download fees  
1083.36 -> so downloading Apache maven this is a latest  version of me one so here there are files are  
1089.21 -> available so hundred links right so these are the  files we have to talk so currently we are working  
1093.95 -> on Windows so we have to download only the zipped  file to download only zip file so this is the one  
1100.49 -> we need to download and this is a source file  Isis is a source we should not know about this  
1105.59 -> they will give you the complete code everything  we don't require the coal we need only binary  
1109.88 -> binary means a jar file ok so this is the one  we need to just down so once you click on this  
1116.09 -> it will start downloading your a passive May one  and it is available as a just zip file format so  
1122.51 -> let me just give this link direct link so just  download that is the first step okay a one on  
1130.55 -> link this is the link direct link from there  you can this is star dot in G del G Jade right  
1140.42 -> so not this one we have to download the second one  binary jib archive second one we have to download  
1145.88 -> not this one so this is a bin dot zip file so  basically we will get a zip file once we are  
1152.99 -> downloading so what you guys can do is you have  to extract the zip file I'll show you already have  
1158.81 -> the download so let us go to C Drive and the  drivers I kept T here as Pio i patch in May 1
1172.94 -> okay so once you get the zip file you have to  extract that zip file so once you extract air  
1181.28 -> you will see folder so you have to keep those  folders in the C Drive so you can see this is  
1185.63 -> the 4 so keep everything in the sea driver  suggests you can keep everywhere but that is  
1191.03 -> little difficult to remember all the paths so I  suggest to keep the folder here itself so once  
1196.85 -> you get the zip file right once we have downloaded  the zip file extract that file and then you will  
1201.65 -> see this Butler folder so just copy this folder as  it is in the C Drive so normally when you download  
1207.74 -> your jeep files it will be there in the download  section somewhere pike so like this so here itself  
1212.24 -> we can just extract like this ok extract it now  we'll get a new folder like this so copy this  
1218.45 -> folder ctrl C and go to C Drive and keep it here  ok this is the first step we need to do and the  
1225.08 -> next thing is we here we don't need to do any  kind of installation so installation innocent  
1229.82 -> just we need to do a simple configuration you have  to download the zip file extract the folder keep  
1235.43 -> it in the C Drive then we have to configure the  path that is very very important so go to where  
1242.18 -> maven so this is bin folder right inside the bin  only all the libraries and commands are available  
1248.51 -> so just copy this location till here and now this  PC go to properties so how we have configured Java  
1256.64 -> path in the same way we have to configure some  a1 path now click on advanced system settings  
1262.37 -> so now you will get this window go to environment  variables now here inside the system variables so  
1271.01 -> you have to do one thing here so that is go to  your path variable so let's go to path variable  
1278.45 -> 8 it ok so once you edit here you have to just  copy that fun so the cop you need to just copy  
1286.04 -> just location so I already copied somewhere here  ok so yeah this is a file this is a location  
1294.83 -> Apache maven 3 dot Phi dot 4 /b ok so till beta  for Laurie how to copy everything this is very  
1302.09 -> very important and not only this you shot you  drop you should also copy or till this one so  
1308.09 -> this is one path this is one path you have to  create and along with this you need to also  
1313.4 -> create one more variable because in the changes it  will be very very useful so there are two things  
1318.35 -> m to underscore ago Navan underscore oh these  are the two additional variables how to create  
1323.69 -> along with the path past available by default  you will be there so very important you have to  
1328.94 -> carefully update this path if I do something went  wrong here some application is stopped working in  
1334.85 -> your system okay so please care if you do this so  first step go to path and edit and click on the  
1340.61 -> new and copy the path whatever you have done  till bin folder this is the first thing and  
1344.96 -> once we have done this then here itself under  system we will create a new variable click on  
1350.72 -> the new and here type of maven underscore all are  uppercase letters and one more time here copy the  
1357.71 -> same path but don't put the bin folder just say  for me till the path okay this is the one where  
1363.83 -> we have to create as soon as you click on this  okay it will show you a new variable like this  
1368.12 -> so you can see here maven underscore home and  another variable also you have to create M to  
1373.55 -> underscore m to underscore and here also you need  to keep the same but don't put any bin folder so  
1381.41 -> these are the two additional variables you have  to add but we thought these two variable also it  
1385.79 -> will work but in the Jenkins it is required so  that's the reason before itself I'm adding I'll  
1391.34 -> show you here itself so these are two additional  variables you have to create m2 underscore main  
1397.07 -> underscore home so once you created this again go  to path variable okay so if you notice percentile  
1405.56 -> and maven the same variable I have used here maven  underscore home percentile person that I put here  
1412.01 -> and M to underscore home so percentile in 204  percent is slash bin Abi idea so I can just add  
1419.3 -> these two entries in the path available one more  time so once you created these two variables and  
1424.16 -> add those two variables in the path field again  you have to click on the new add percentile like  
1430.52 -> this and then a one underscore oh this is a one  variable how to add and the other way other is  
1439.28 -> again percentile m to underscore a one and  percentage so person is representing this  
1448.37 -> current directory okay slash bin for now so back  - backward slash ding so these are the two paths  
1456.52 -> we have to add so this is very very important so  I will just remove from them so I already have  
1462.46 -> this and just remove them alright so don't forget  to add these two available very very important I  
1468.37 -> will just show you once again so this is the one  this is the one let me just take the screenshot  
1475.15 -> and I will just give it to you so don't forget  this this is the configuration of maven once you  
1482.5 -> copy it the zip file and then you have to do all  these things let me just take the screenshot right  
1490.93 -> so what you have to do here is you have to create  these two variables these are the two variables  
1496.3 -> how to create newly and the path variable you  have to update this one and what else we have
1507.67 -> yes this one okay these three things because these  things are blocked it okay click on the new button  
1517.42 -> here and then oh give order so actually these are  the two things are referring here okay so just  
1524.65 -> copy the screenshot I'll send it to you so this is  a one underscore screenshot all right here so this  
1534.49 -> is the configuration you have to do one time so  once we have done this then we can check whether  
1539.38 -> the Maven is properly installed or not so how we  can verify it is very simple just go to command  
1545.83 -> prompt CMD and open your command prompt like this  so once you have open your command prompt so here  
1554.17 -> just type a command so what is that command is MV  and - version mb n - version so when you run this  
1564.61 -> command okay so it will show you the ambient of  mavin version so now we can see here this is even  
1572.74 -> mavin version this is your maven mission and when  you run this command also here you will see an  
1579.13 -> error first time so what is an error is same ever  again so when you run your test case from a1c la  
1584.95 -> you have to install the me so first I'm gonna run  em V inversion command so whatever we already have  
1590.98 -> seen in Eclipse so see a mirror you will see in  the command prompt so no compile is provided in  
1595.66 -> this environment perhaps you are running a jihadi  rather for JD so and when you get this error you  
1601.39 -> can see here JRE path instead of JDK currently  have a JDK path so it is fine but in your case  
1607.51 -> it will be JRE path if you are getting an error  so if you want to fix this error just you need to  
1613.48 -> just configure the Java home so let's go to again  your this PC properties advanced system settings  
1621.73 -> and go to environment variables and here you can  see Java underscore home variable I created so  
1628.75 -> you have to give the path till Java JDK okay and  once you created this new way how to create this  
1634.63 -> click on the new and just type in Java underscore  home and give the location of your Java till JDK  
1641.65 -> folder and once we have given this and then go to  path variable okay go to path variable edit now  
1649.48 -> here I am referring this Java home so now I can  see this one person tell Java home and personal  
1655.3 -> Java home Lib directory so both they have to refer  so these are the two things we have to do if you  
1661.12 -> are getting that error okay and now I'm closing  this so currently have configure the JDK so fine  
1668.62 -> it is not giving an error so this is the first  verification point so once you have installed  
1673.48 -> this maven so how we can verify this we have to  just type MDM - version Emma ambien - version  
1683.35 -> tonight so this will give you the version number  of a one and everything is fine so now you are  
1690.94 -> able to you will able to execute our test cases  through command calm so before that you have to  
1696.52 -> do all these configuration make ma one everything  is ready so this is how we need to do just to make  
1701.41 -> one installation so have given each and every step  clearly so run the test cases through me one CLA  
1706.78 -> first you have to install me one on Windows  operating system you can download from the  
1710.74 -> sink ok and then you have to configure the path  right click on my PC advanced system environment  
1715.72 -> variables you have to create as a set or a one  passenger and then check the world service install  
1723.16 -> or not may one install or if you are getting  this error we need to configure the part Java  
1728.32 -> Java quark okay done so now let us see how we can  execute our test cases without having it so now  
1734.95 -> currently my project is here let's capture the  project path so the path is very much required  
1740.47 -> so this is your current path of your project so  location of project this is very very important  
1749.8 -> because we are referring this location multiple  places so once we get this location we don't  
1755.53 -> require this Eclipse so I minimizing this right  so if I open this particular folder in the Windows  
1764.23 -> Explorer this is your current project right so  here we have a pom products and I'll test ng  
1769.57 -> everything so here we need to open so we can also  open here also but we need to first go to your  
1776.44 -> project directory so how we can go to your project  directory command is C and give the path this is  
1783.58 -> the first command how to give now press enter now  you are entering to the current project directly  
1789.79 -> so in your windows wherever you are it doesn't  matter in which order directly or whichever folder  
1794.89 -> doesn't matter if you run CD and given complete  path of your budget it will directly navigate to  
1800.5 -> your project location okay so here we have to  run our comrade examine so through maven come  
1808.3 -> on so here we need to run we need to execute  upon command here in the command prompt so the  
1813.67 -> command is MV n clean install this is a command  so there are two commands actually first clean is  
1821.32 -> a command it will clean up all the previous stuff  and then freshly it will once you clean that all  
1828.46 -> the execution stuff the previously whatever we  have done and again it will start execution of  
1833.62 -> complete project using this install command now  let us try to execute this command mb n clean  
1841.72 -> install this is a command ok now I'm completely  minimized my eclipse right so now I am going  
1850.3 -> to execute to comment on this is only my command  observe this what will happen so a pressing enter  
1856.69 -> here so as soon as a press enter it is started so  let's see how it will excuse now it is started so  
1864.91 -> you can also see the UI so after exhibiting few  statements before and it will now we can start it  
1870.76 -> so now you can see the same laws whatever we have  seen in the Eclipse we have seen and it is also  
1875.08 -> launching my browser so it is large to my browser  my test case or exhibit and you can also t really  
1881.77 -> read all the log messages here whatever launch  we have created in your desk case is the logs  
1887.62 -> messages will be appeared in the console window  now you can see my test case is executing here
1893.35 -> so running your test to suit okay first a test  case is completed now it is started second test  
1904.63 -> soon it should give all the logs actually so  we will run one more time and see so now it is  
1910.72 -> executing second test case okay so once it is  successful now you can see will success message  
1926.29 -> here okay something went wrong actually now it  is giving the messages so actually we should  
1934.87 -> see these messages okay so building successful  means all my test cases are executed so again you  
1941.56 -> can see all the message have been logged here  but these message should log at the parallely  
1946.42 -> as soon as my desk is of executes if something  went wrong at so let me run one more time so  
1952 -> I'm just clearing this CLS and one more time  I am executing a one clean installed now press  
1958.69 -> enter okay now there are expect some statements  okay now it is started running test suit so only  
1974.44 -> local connections are allowed now you can see  so there are some statements are logging in  
1979.21 -> here right so parallely my browser is opening  all these things so now by religious messages  
1983.95 -> you can even understand what is going on on  the SK side providing the username providing  
1989.05 -> the password clicking on the login button the  login is successful so fastest case is committed  
1993.46 -> now it is started another risk case so we can  just carefully read that log messages if there  
1999.79 -> is something meant you can see the log messages  and clearly understand what is went wrong here  
2004.38 -> ok providing the customer details and the desk is  passed and now finally we get the build success  
2016.29 -> so this is all or if you something is went wrong  it will give you build failure ok now where we  
2023.13 -> can see all the reports and everything on the same  project directory itself so from where we have run  
2028.32 -> this test case so from this particular project  directly itself right so let me open this one  
2034.74 -> one second just a moment so where is our project  the current directory is this is our location of  
2044.94 -> your project so let's go to your project so here  under where test type and output these are the  
2054.69 -> reports are generated so this is a report just now  generated this is the latest report let me remove  
2059.49 -> all the reports ok so it will generate a fresh  report so once again I'm a running my test cases  
2066.15 -> let's clear everything seal this and then okay and  clean you so now we can see so my desk is a given  
2080.58 -> exhibition is completed we can see the new report  here on the same project folder under test I for  
2087.33 -> not for now I'm just realizing this now my test  case is started running I am in able to edit event  
2102.84 -> this case because it will take some time so the  thing is not just to disable that you guys can run
2107.4 -> [Music]
2107.46 -> [Music]
2111.48 -> okay so now everything is done right so let's  go and see the report now so now you can see  
2134.61 -> the new report is generated under test I have an  output your project derivatives now we can open  
2140.37 -> with Google Chrome or some browser you can use any  browser you can visit so now to discuss are being  
2147.36 -> executed and passed alright so this is how we need  to execute your test cases through command prompt  
2153.57 -> run your test cases using command Ron without  using eclipse so what we have to do for this  
2159.63 -> be here to install the me one software on Windows  then we have to configure the parts then execute  
2165.99 -> this command to come on Chrome so first we need to  go to this vector location wherever your project  
2170.88 -> is located and then you have the is good may 1 MB  a min sulayman so ambient feel installed so this  
2177.54 -> command we have to execute so what this command  will do internally is it will again in sequel  
2182.34 -> format xml file internally this command will exude  politics there's only now so in this approach i  
2190.05 -> am just writing this commands manually right so  i'm just CD and providing the location and then  
2195.12 -> I'm giving this command manually in the command  prompt so I don't want to even write the command  
2200.01 -> in command prompt I don't want to even open my  command prompt window so when I do one click on  
2206.25 -> the simple one file it should automatically open  the command prompt and it will start executing for  
2212.07 -> test cases that's how I need to do automate so  how we can do is let's close this window so in  
2218.43 -> the same project directory itself ok go to your  project location here I will create a new file  
2225.18 -> called as a bad file that's what bashfully is  nothing but exhibit of the ok in Windows we can  
2230.46 -> call it as a back dot bad is an extension and  in other operating systems became called as a  
2235.8 -> hostage if it is a Linux or UNIX we have a shell  script file we can call as dot sh is a extension  
2241.14 -> so here how to create the bad fact so there is a  third of so in the third approach we'll see how  
2248.52 -> to run a test cases using the run dad bad so you  can you can give any name to this Matt fine but  
2255.39 -> usually people will do a run dot bath because  this will run your test cases or test suits so  
2261.48 -> let me just create run our bad file and save the  project Derek so here new and first take the text  
2270.6 -> to document itself okay by default it will give  a dot txt okay so we need to rename this so this  
2276.87 -> will I name is a run dad but run dot button remove  the dot ext remove dot ext extension okay the icon  
2285.66 -> will be different so for underbar fat icon will be  different and people will do a lot of people will  
2290.76 -> do some mistake here so don't create the text file  it should be bad fine okay so run here right click  
2297.33 -> here and edit it will open up enough notepad just  like this but even though if it is open in the  
2303.57 -> notepad it is a bad file okay so whatever commands  we have typed in the command prompt the same  
2309.93 -> commands you have to give here so CD what's the  command we have given to navigate to the project  
2315.6 -> directory CD this is a location we have given CD  the location of your project and what's the next  
2322.41 -> command we have given MBN clean install this is  another so instead of writing these two commands  
2329.91 -> in the command prompt I'll keep those two commands  in the Rundle bad fan okay so once we have saved  
2335.7 -> this so now the rendered bad fell contains  into commands right so when I double click  
2340.83 -> on this butler file it will automatically open  the command prompt and it will execute the same  
2345.36 -> commands so instead of manually typing all the  commands the runner bad film keep those commands  
2351.48 -> and under bad will will execute those commands  Auto many okay now on the test - report - only  
2357.81 -> one repo to have so now how we can execute this  just double click on this just double click now  
2364.56 -> it is started a command prompt like this now you  can see the same command is accreditor CD this  
2369.81 -> one and then ambient clean install command all  right now it is started executing my test cases
2378.29 -> in the same way whatever we have tried it earlier  oh it is launching my webpage now we can also see  
2384.08 -> all the logs in my command prompt okay now first  a test case is done the starting second test case  
2402.98 -> ok automatically this funding will be closed once  it is successful closed window is automatically  
2427.13 -> closed we don't need to open and we don't need  to close ok there's a user so usage of run mad  
2432.02 -> paddle with the singles like everything will have  suppose you have 100 test cases under test case  
2437.45 -> we will go and execute one after another ok so  there's a meaning body and so from our back side  
2443.87 -> so now we are able to execute three different  ways one is in between eclipse we have executed  
2450.74 -> through form dot XML then through command prompt  we have executed using commands and the same  
2456.86 -> commands are kept in Condor barfed all right and  then we have experience so under under God filled  
2462.89 -> contains not bad file contains two entries so  what are the entries see and location of your  
2469.7 -> project and then MVM clean install so these are  the two commands which we need to add in there  
2476.3 -> are not back that's it ok now we have seen the  different approaches and next level is run the  
2484.67 -> automation to run dot bad file also we have seen  the next thing is coming to the changes so here  
2490.31 -> the continuous integration will start so here  the continuous integration will start so this is  
2496.52 -> very very important so we have already done this  and now you're in the Jing is part now you're in  
2501.65 -> the Jenkins path so I'm directly jumping into  continuous integration so here we'll discuss  
2505.7 -> they can be already discussed may 1 now I'm going  to discuss about the Jing is part ok now what is  
2513.59 -> come to before execution before running your test  cases through Jenkins right so while the Jenkins  
2519.98 -> is required wiving in to execute or test cases in  these many ways that we need to understand so to  
2526.82 -> understand this we need to first discuss about  continuous integration process please reason  
2533.78 -> this one this is actually happening coming up so  in the real-time environment basically there are  
2539.27 -> three important teams will work together so one  is developers ok development is one team and a QA  
2548.42 -> is another team ok so between these two teams  there will be another team called as a DevOps  
2554.03 -> called development operations so these people are  responsible for integration stuff like they will  
2560.93 -> assist some they will perform certain tasks from  the developer and they will perform sit and - from  
2565.7 -> the QA so they will bathe basically share the  tasks between QA and dev ok so let's see each  
2572.42 -> and everybody's role so every day means contains  set a number of people right so what the devil is  
2578.24 -> responsible for it is the dev is implement the  code so to develop the application they have  
2584.63 -> to write all the dead code right so the dev  team will implement the code by using set in  
2589.4 -> programming languages they will basically write  the code and at the end of the day so there is a  
2594.92 -> developer means there will be different developers  will be there not only single person right so all  
2599.6 -> these people at the end of the day they will keep  their code in common place this is called as a  
2606.8 -> repository this is called as a common repository  I'll tell you this one and tomorrow session in  
2613.79 -> detail for now just understand this is a common  repository the positive means is a place a common  
2620.09 -> place and everybody can share that so everybody  can share those files and they can put their  
2626.3 -> files in this particular repository this is called  common repository and everybody whatever whoever  
2631.67 -> is done the tasks and completed they'll keep  their code in this particular repository that  
2636.71 -> was called common shared repository so common  shared repository now from once the code is  
2643.94 -> checking this for checking process chicken is  nothing but whatever poor they have completed  
2648.75 -> they will keep that for of they will copy that  code in the repository that's called chicken  
2652.98 -> process so once the developer Chickering their  old what the dev ops team will do is they watch  
2660.36 -> team will pick up that particular code they will  do all the integration part then they will create  
2667.44 -> a be reader so because we don't get the program's  directly from the developer okay so DevOps team  
2674.4 -> will create a builder after integrating all these  programs and they will take all the code from the  
2680.85 -> repository and they will make a build build is  nothing but a final integrated product normally  
2687.21 -> it will be an exe file or sometimes it will be MS  FL or some other form it is just an installer file  
2693.66 -> we can just get it handed double click and start  installation so this is just the installation  
2699.45 -> file installer file we don't get any code from  the developer ok so who is we will create this  
2705.27 -> partner build dev ops team will create this cattle  feed so once the build is created so this is the  
2710.76 -> main task they will do from the developer point of  view but actually build should be created for the  
2715.71 -> developer by the developer right but the develop  C will take responsibility of this so dev ops  
2721.59 -> team will take that code from the repository and  they will create a build so once they created the  
2728.55 -> build okay this is from table 2 or dev ops now  come to the Q Bar so QA what the QA will team  
2735.03 -> is responsible for and QA also there are multiple  people who are working under multiple test cases  
2740.52 -> fight so as soon as they have completed their test  cases automation test case I'm talking about so  
2746.76 -> whatever the test case is they have completed and  here also we have a common repository here also  
2753.12 -> we have a common repository so everybody in the  team will check in their core automation code in  
2759.06 -> this particular repository at the end of the day  whatever we have completed the code or automation  
2765.06 -> test cases will be part of this particular common  repository now once the dev ops team is created  
2771.18 -> this build right and at the other other side the  dev ops team itself will take our core automation  
2777.78 -> code from this positi and execute our automation  code again as this build so this automation will  
2784.77 -> be executed against this field so here itself the  sanity and smoke testing will be completed so what  
2791.25 -> is sanity testing means the basic functionality  testing whether the build is properly installed  
2796.5 -> or not and basic functionality is working or  not we can verify here itself and here this is  
2802.14 -> the responsibility of the DevOps not the qat so  before Q is getting the build itself and it will  
2808.74 -> automatically verify the basic functionality  okay so what the DevOps team is doing here is  
2814.17 -> they are creating the build by taking the code  from the developers and also they are executing  
2820.32 -> our automation on the particular build after  taking our code from the common repository  
2825.78 -> so the DevOps is helping the QA as well as a  developer so what is the use of this one is our  
2832.26 -> process will become very faster ok in the agile  process especially things will go very faster  
2838.2 -> so developers team in polyworks and QA team is  also parallel he works there will be some team  
2844.32 -> is required here so they will coordinate between  the QA as well as Tim okay so what the DevOps team  
2851.58 -> responsibilities is mainly integration purpose  so they will integrate all the day or creation  
2857.61 -> of the build okay Automation of builders so we can  simply say build automation build automation will  
2863.67 -> is different a functional testing automation  is different so basically the DevOps team is  
2867.96 -> responsible for build automation means they have  to create the build based on the programs which  
2873.72 -> are created by the developers now they will take  our automation pool from our common depository and  
2878.94 -> they will execute our automation code on the build  and once the build is successful basic automation  
2884.58 -> is passed and everybody in that team DevOps qe8  there everybody in the team will get automatic  
2891.48 -> email so build is successful and then QA team  will download this build in their environment  
2897.54 -> and install in their environment and continue  the rest of the functionality or bugfixes build  
2904.14 -> is nothing but sometimes you can have bug fixes  sometimes if you have a new features implemented  
2908.73 -> by the developer so those things will be tested  in the queue again once they have passed they  
2915.22 -> have immediately automail doshas cases again they  have to check in their code latest code on the  
2920.62 -> common equality and ruin the second round again  the developers also created the new code again  
2926.14 -> they will put in the repository in these things  will happen in day to day basis okay suppose so  
2931.75 -> the developer started morning at 9:00 a.m. and  the shark 5:00 p.m. they have chicken in their  
2938.41 -> code in the repository okay now what the dev ops  team will do is here these are a people action so  
2944.56 -> those people don't even or manually so they will  do everything is automation so here to creation of  
2950.92 -> the bill they will use male 1 software and to  run our automation in the build they will use  
2956.53 -> change means so here the main thing is will come  into picture so actually me one and jenkees our  
2962.95 -> DevOps tools or we get say continuous integration  tools basically maven is purely build automation  
2969.94 -> tool May 1 is a purely build automation tool  but as a tester we are using just a few number  
2976.57 -> of feature from mavens just updating form that xml  running or disk cases of command so these features  
2981.94 -> are already there in the main one so we are just  using only 5 to 10% of the creature from the maven  
2987.22 -> we are not using hundred-percent features but  the divorced even use all the feature from the  
2991.96 -> mean one and by using this maven they will create  the build they will integrate all the programs and  
2997.45 -> finally they create the pill so how this will be  done by using maven software so divorce will use  
3003.21 -> this level very effective and Jenkins is a tool  they will use to run our automation code on the  
3010.68 -> bit and once the build is successful and our  automation is executed the final will be final  
3017.28 -> bill will be read in the Jenkins itself so we  have to download the Jenkins build and in your  
3022.29 -> queue environment and mean to test in the next  day morning suppose my name to 5:00 p.m. they  
3026.97 -> are working right so the 5:00 p.m. exactly the  how it's a queen they according the repository  
3031.05 -> and from shark of I to next to day morning so  between completely night the entire night the  
3038.1 -> DevOps automation will run so integration of will  happen automatically parallel or automation code  
3043.77 -> is also Xzibit automatically but the end of the  next day or beginning of the next today so next  
3049.75 -> to the morning at sharpen I name them we will  get an email from the DevOps so your build is  
3054.91 -> successful and you can just download and test it  and next today morning so before day 9:00 a.m. to  
3060.25 -> 5:00 p.m. they are working on some features and  the next today morning we will get those features  
3064.57 -> from the DevOps the complete build which contains  the new features now we are casual apparently we  
3069.7 -> are going to test that one and when testing that  Butler bill as soon as anything is passed new  
3075.73 -> test is have be automated and then again check  into the common repository again parallely the  
3081.52 -> developers is work on another new features or bug  fixes as soon as they have done some fix or they  
3088.21 -> have implemented a new feature will be part of  this repository at the end of the day and these  
3093.43 -> are continuous activities every day every day will  happen if we read above steam will run this take  
3100.03 -> this bill run this build create the bill Jenkins  it will take the Jenkins will run our automation  
3105.1 -> code on the build so everything will happen day to  day pieces and sometimes for a day two times will  
3110.32 -> happen that depends on the infrastructure all  the planning okay so this is called continuous  
3117.4 -> integration process so from the dev divorce and  q8 so these two teams effectively working together  
3124.33 -> for one project and in agile process whenever the  agile came into the market continuous integration  
3131.11 -> processes become very very popular so nowadays all  the companies are following this process so now  
3137.53 -> the main intention I am saying this one is where  we have to use all these tools okay so maven is  
3143.71 -> Jenkins is a mainly used in DevOps team we are  not hundred percent responsible for Jing it's  
3148.63 -> an amoeba we use it in feature from Jenkins and  maven but actually running by the divorced okay  
3154.84 -> this is called continuous integration process  so now why we have to exhibit our test cases  
3159.76 -> using Jenkins the third approach because DevOps  team will exhibit our automation test cases only  
3166.33 -> through Jenkins but what is our role we have to  keep our coding the common repository we have to  
3172.42 -> do certain configuration of the changes we have  to take all that we need to take the ownership  
3177.01 -> of our configuration okay and then from onwards  Ottoman and even DevOps team also will not run  
3183.07 -> automation the automation plans automatically  happen based upon the schedules they will sit  
3187.57 -> sit in time okay based upon the time Jenkins will  exhibit out this case it's automatically but our  
3193.33 -> QA responsible thing is we need to just configure  these things you have to keep our record in the  
3198.1 -> common repository then you have to configure  this path and everything in the Jenkins okay  
3203.02 -> please we have to do some trial run and from then  onwards the develop team will take care of it okay  
3207.82 -> so this is one time qualification algorithm so  that's the reason we should make sure our test  
3213.85 -> cases should be able to run on the Jenkins and one  more important thing there is jinkies whenever you  
3220.6 -> exhibit about Jenkins in that environment you  don't see any UI so it is completely headless  
3225.97 -> execution headless means we don't see any UI part  everything will happen at the back end itself but  
3232.51 -> automation cases will run you can see all the  logs what is happening at the back and we can  
3236.65 -> see that but as a user I don't see any kind of UI  so that's the main beauty of Jenkins so because  
3244.12 -> it is not showing any UI the execution will be  very very faster everything will happen in the  
3248.65 -> back in itself okay that's the main feature of  the Jenkins so everything will execute using  
3253.78 -> seamlessly everything is exports seamlessly in  Jenkins okay so now we will see how they exhibit  
3261.58 -> our test cases using Jenkins doesn't next one  right and we have to install Jenkins software  
3268.33 -> so Jenkins is available as an open source tool and  but in the real environment you don't install any  
3274.39 -> Jenkins in your system very very important  so Jenkins will be owned by the DevOps team  
3280.12 -> ok so they will install in their environment and  they will just give the URL to you to access the  
3285.07 -> thing it's so once you get the URL from the Jing  because this is web-based application ok because  
3291.19 -> this is a web-based application so we'll just get  a URL from the DevOps team and by using this URL  
3296.62 -> you can access the jiggy's application just like  other web server we will access right using you  
3301.57 -> are in same way you can also access Jenkins who  you are and you can will be provided upon URL or  
3307 -> you will be provided with username and the login  so by using username and login just log into the  
3312.83 -> Jenkins and you can add your project and do the  configuration there's only one time job so until  
3318.2 -> unless your test cases are failing in the Jenkins  they don't approach you again so when the dev ops  
3323.3 -> team we will approach you sometimes your desk s  will fail in Jenkins sometimes then you have to  
3328.61 -> do certain kind of analysis so why it is failing  is that because of configuration issues in Jenkins  
3334.52 -> or is there any issues with the test cases or  sometimes application is changing something  
3339.68 -> okay so these are all things we have to analyze so  only in that particular scenario or that practice  
3344.69 -> situation the dev ops team will interact with you  or they will come in get with you okay so under  
3350.15 -> knowledge once we have done the configuration in  Jiang is there is no much role in the DevOps team  
3355.82 -> QA Road so just we need to automate the dis case  from day to day basis whatever is completed keep  
3360.68 -> make sure they are ready in the common repository  so Jiang is automatically pick up from there and  
3365.21 -> execute your test cases and tomorrow we'll  discuss more on these two what is commonly  
3371.69 -> positive I will do how we need to put the core  there and everything but today we will see how  
3376.22 -> to execute our test cases in Jenkins because this  will be part of maintenance ok so check in the  
3382.4 -> for check out the core so how we can put the code  in the common depository or if you want to modify  
3387.2 -> something how we can do this how the Jenkins will  take the pour from this one so we'll see that in  
3392.09 -> the next session that's called maintenance PAP  now we'll see how we can execute our automation  
3397.94 -> through Jenkins okay so first of all we need  to install the Jenkins part so to install the  
3403.37 -> Jane case we have to go to this party where I've  captured each and every screenshot because this  
3408.44 -> will take a lot of time okay almost Jenkins will  take 15 to 20 minutes of time to install complete  
3413.09 -> but in the real time you don't install anything in  your local system for practising purpose you can  
3418.64 -> do installation because this is just open source  tool we can install and you can work with this  
3423.83 -> okay but in the real diamonds dev a stream is  owned by this tool so you don't need to install  
3429.05 -> anything all right so now let us see how we  can download Jenkins and how we can install  
3434.54 -> it this is a link step by step installation just  go to this particular link now this is a working  
3442.34 -> insufficient website okay so from this putler  website we need to download thinking software  
3448.67 -> so from where we have to download so they have  given so many things like a weekly religious  
3454.34 -> they have and long-term support also we have so we  have to always download from this one so download  
3459.77 -> jenkins longtime support and most of the times  weekly religious having some issues every time  
3465.86 -> so I face a lot of issues in the weekly releases  so just go to the long-term support because these  
3471.5 -> are unstable builds stable ones okay so just go  to Windows currently we are working on Windows  
3478.88 -> so click on the windows it will start downloading  zip file now we go you got the g1 right so this is  
3487.04 -> a different one 18m it will take some time so  just cancel this because I already have it so  
3491.84 -> ok so this is a link we are too used to download  the jig this is a fourth approach to run tests is  
3503 -> this using engines so first of all we need to  download the Genki so this is URF application  
3513.35 -> so this is a sorry no this one this is about let  me copy this let it get it from here this is the  
3526.73 -> or URL or I can just get provide this link copy  this link ok so this is a link so once you have  
3533.96 -> opened this part in our link then you will start  installing you will get the jib fine so once you  
3539.15 -> get the zip file and just extract that zip file  now you will see is like this so let me just show  
3546.8 -> you so this is once you have extracted your zip  file you will see one folder like this jakey's  
3552.2 -> and some folder and open this folder then you can  see one MSI file so MSM is Microsoft install it is  
3558.62 -> almost equal to Exe file so you will get this exe  file they can message map just you need to double  
3564.47 -> click on this file okay then installation is start  so the instant ups feels will be like this so as  
3570.5 -> soon as you click on that file you will get this  but less thing so you need to go step by step so  
3575.09 -> click on the next then click on the install  then it will this is a default location where  
3580.48 -> the Jenkins will be installed now click on the  next and the next step then click on the finish  
3586.33 -> there are only four things you will have so now  you are installed Jenkins so this is very very  
3591.76 -> simple but the configuration will take a lot of  time so installation is rigged is very simple  
3596.95 -> what we need to do set in configuration so I'll  show you that configuration so here come back  
3605.41 -> okay so same thing is internists presentation so  how we can do this Jenkins configuration so asanas  
3614.11 -> we have installed over Jenkins because this is a  web-based application you should be able to access  
3619.09 -> using this particular URL ok so HDB localhost  but in real time they will give you this URL to  
3626.26 -> you okay using that word Allah can access this or  to when you install your Eclipse when you install  
3631.03 -> janeen's in your local system first time okay  when you open this URL the first time it will  
3636.22 -> show you unlock Jenkins so this is a screen you  will see unlock Jenkins so here we need to provide  
3643.78 -> administrator password so where we can find this  administrator password so to unlock the jakey's  
3650.8 -> we have to provide this administrator password  so this administrator password will be provided  
3655.93 -> inside this Jenkins installation location so once  you go to Jenkins installation location so here I  
3664.18 -> have a Jenkins there is a one folder called secret  folder so we can see secrets right so inside this  
3671.44 -> folder you will see currently I don't have that  one because I already use or that key so but in  
3677.74 -> your case it will show you initial admin password  so this is a one it will show you for you initial  
3684.31 -> admin password just open this in your notepad  somewhere and just copy the text whatever they  
3690.52 -> have given and put it over here okay and then  click on the continue and then you will be able  
3697.33 -> to unlock the Jenkins only once you have copied  this password here this file will be deleted  
3702.37 -> automatically so for me already user that is so  that's the reason it cannot see this one initial  
3708.01 -> admin password is a file name so where you can  find this this Butler location under C Drive  
3713.8 -> Program Files x86 Jenkins and secret folder  so once you provided this password here your  
3720.61 -> Jenkins will be unlocked so copy this here click  on the continue then it will start configuration  
3726.67 -> so it will show you two options install suggested  plugins or select the plugins to install so just  
3733.87 -> go for first option because we don't know exactly  what are plugins we require so we can just try to  
3738.49 -> install all suggested plugins by Jenkins so  select the first option click on this but  
3744.31 -> this is basically a button just click on this  now it will start installing required plugins  
3749.89 -> within Jenkins so here it will take some time  maybe one or two minutes it will take so each  
3755.53 -> and every plug-in will be added to your changes so  after that it will give you one more screen this  
3763.27 -> is one continuous screen ok one after another it  will be displayed so under Jenkins configuration  
3768.46 -> again it will show you create first admin user so  so far we don't have any user for Jenkins ok but  
3775.63 -> here we need to create the first admin user this  is we have to create carefully so as I suggest you  
3780.97 -> just admin admin admin admin easy username admin  is a password and give some email id and it will  
3787.96 -> be created admin user so with this admin user  later you can create any number of users user  
3793.39 -> in the sense he can able to log into the Jenkins  ok so we can create any number of users in Jenkins  
3798.73 -> but admin user must be there so administrator  only can create other users and he can admin  
3804.52 -> or he can manage everything in the changes but  rest of the gates don't have all the privileges  
3809.11 -> even in real time diversity will you provide you  login but still you cannot access everything in  
3814.27 -> only your project stuff in Jenkins there are  n number of projects keep on running even from  
3819.73 -> other teams so in the Jenkins whatever project  you are responsible for so you can see only that  
3825.43 -> but left quadrant other projects you cannot see in  the Jenkins because of restrictions access level  
3830.83 -> restrictions ok but admin user can see everything  and you can also lose it in configuration within  
3837.16 -> the eclipse within the Jenkins so once we have  selected once you have provided this username  
3842.08 -> password everything and click on save and continue  ok then it will take some time here finally we  
3847.52 -> will get instance configuration it will show you  Jenkins URL like here and then save and finish so  
3854 -> this is the URL they have to use every time to  launch your Jenkins application and login to a  
3859.07 -> [ __ ] in application with this admin user so  whenever you providing these details you have  
3863.36 -> to make note of this okay because sometimes if you  follow that then again you have to install Jenkins  
3869 -> if you forgot those menus remember now click on  save and finish now it will be installed so now  
3876.23 -> we need to do set in configuration inside the  Jenkins ok so you will get this Jenkins ready  
3881.99 -> so once you have log into Jenkins you will see  the dashboard this is called Jenkins a dashboard  
3886.07 -> so now I am going to show you my Jenkins go to  google chrome my I'm opening my Jenkins so how  
3893.51 -> to open localhost colon 8080 so Jenkins will run  on a 0-0 default so press Enter now it will be  
3903.23 -> open your Jenkins ok so it's not so it cannot  be reached okay if it is no we are getting some  
3911.87 -> connection issues like this just go and restart  your Eclipse restart imaging it there will be  
3917.12 -> service created in the windows go to services and  open there's a run as administrator so go to the  
3924.8 -> services and then restart the Jenkins a service  so as soon as we have installed Jenkins it will  
3931.85 -> create in new so now you can see my Jenkins is  currently not running so the reason I am NOT  
3937.28 -> getting the URL so since the Jenkins service  and click on the start so by default it will  
3943.97 -> be up and running but intentionally have stopped  engine so once it is started running now you can  
3948.89 -> see three buttons you can always stop and do you  start anything you can do so once we have started  
3953.3 -> it just wait for one or two seconds and then  try this URL one more time ok so still it is  
3961.94 -> running so that's the reason it is not it open  take some time few minutes time it will take so  
3969.35 -> this is all configuration part ok so now it is  pinging this URL let's wait for a few seconds
3979.46 -> so before getting the login so we have to do all  this configuration step mister please do carefully  
3986.48 -> if we miss anything else you do something went  wrong again you have to start from the beat okay  
3991.4 -> so please do carefully and slowly okay now we  have to login to the Jenkins yes now my Jenkins  
3998.96 -> is please wait while Jenkins is getting ready to  work so I have to wait for a few more seconds and  
4003.82 -> it is always a refreshment so once it once it is  refreshing I will get the login screen so once  
4013.3 -> you login so admin user we already created earlier  right so with the same admin user we should able  
4018.61 -> to login to Jenkins so once we log in to Jing  is we can create any number of users so wait  
4029.11 -> for few seconds again let me refresh it one more  time so once it is started it will automatically  
4042.7 -> gives the login screen okay now we got the login  screen so let me log into Jing is admin admin  
4060.1 -> username and password I have given at the time of  installation configuration then click on assignee  
4065.2 -> so once you click on the sign in then you will  see the a dashboard page so this is the dashboard  
4071.65 -> so currently I have n number of projects already  ran this area but in your case you don't see all  
4076.96 -> these things you will see only these options which  are there in the left left side okay these are the  
4082.06 -> only option you can see by Devon you don't see any  projects here this is actual default dashboard of  
4087.55 -> the Jenkins but here I have run all the multiple  projects earlier so that it is giving all the  
4094.03 -> projects like this okay so this is how we need to  install the Jenkins and unlock the Jenkins and do  
4101.41 -> certain configuration and just log into Jacobs but  again we have to do a lot of things inside this so  
4107.83 -> we need to also install maven plugins in Jenkins  because we are using Mae project right in Eclipse  
4114.16 -> so we are going to run Mable project within  Jenkins so we have to also install additional  
4119.17 -> plugins which are required for the main ones so  to install those things we have to go to within  
4126.22 -> the Jenkins we have to go to manage Jenkins so  all the plugins we can install from this man is  
4132.22 -> Jenkins and here this go to manage plugins okay  go to manage plugins so here so here you have to  
4142.84 -> select whatever entry is related to me--one so  I have given all the interest once you click on  
4147.64 -> the maven plugins under available you can  select or maven integration maven release  
4153.52 -> plug-in maven invoker maven repository schedule  cleanup repository connector a one-in-four so  
4160.39 -> whatever option is related to me--one you can see  just select all these options okay and once you  
4166.96 -> selected these options and just they will you will  see one button here let me show you another scheme  
4172.54 -> okay so managing means yes so here you can see a  button so here install without restart so this is  
4183.67 -> actually button installed without restart so once  you selected all the maven plugins just like on  
4189.13 -> install without restart so once you have done this  it will take some time to install all may one like  
4194.95 -> is within the Jenkins so once it is done again  it will ask you to restart your Jenkins again it  
4200.92 -> will ask you to login just for where the admin  admin and click on the sign now again you will  
4206.02 -> login into the Jenkins this is another step we  have within your changes between the Jenkins so  
4211.81 -> because I already have that so I'm not getting  any maven options here so but in your case you  
4216.82 -> will get a lot of my own options select all of  them I've given in the screenshot I so can just  
4221.44 -> go through see its feature and select or whatever  maven options I have selected and then click on  
4226.18 -> download so here you can see one option called  download now and install after restart you can  
4231.43 -> see one of this option here click on this it will  start installing then you can see this particular  
4236.29 -> screen so each and everything will take each  and every option will take some time and you  
4241.42 -> have to wait for one or two or three second  female you sometimes and everything will be  
4246.14 -> successful and then automatically restart jakey's  will be restarted and one more time you have to  
4251.81 -> log so once we have done all these things now  we are ready to run our project who thing can  
4258.17 -> say you can go to dashboard so there are multiple  options are there here just I'll show you what are  
4263.42 -> our options we have to use okay so now we will  see how to run our project using Jenkins how to  
4270.56 -> run our automation using genius I'll show you  now so very simple flow we have two former here  
4277.67 -> run over test cases using Jenkins okay so first  we have downloaded Jenkins we do configuration  
4285.17 -> all the stuff we have done so now let's login  into Jenkins so this is already logging so in  
4293.18 -> the Jenkins the there are two approaches we have  in the two different ways we can run our project  
4297.74 -> within the Jenkins so the first approach is just  go to new item so new item is we have to create  
4304.88 -> the new project within the Jenkins so here I  am giving some name to your project so here n  
4310.82 -> would be commerce and just there are two options  are available free state project maven project  
4317.48 -> within the Jenkins itself we have it two types of  projects one is free sale project may one project  
4323.66 -> if I take freestyle project we can run run a bad  friend which you have already created earlier and  
4329.45 -> if I take maven project we can directly run  our combat XML file so there are two options  
4334.82 -> but in the real time we always use maven project  okay but I'll show you both of them so freestyle  
4342.95 -> project I'm just taking pre and first of all I  need to give some name so what is the version  
4347.57 -> of your project B zero zero one so no commerce  be zero zero one freestyle project so I'm giving  
4354.71 -> some name and then take the Freestyle project and  then poke a better so this is a flow I have given  
4362.21 -> all the screenshot so please follow the same all  right so now are we given the location so here if  
4369.56 -> you want to write some description of the project  you can just write it already leave it so don't  
4373.94 -> do anything else here just directly come down to  build okay so here you have to select one option  
4382.69 -> called execute windows batch command executed  windows batch command select this now here you  
4390.88 -> have to provide the location of your under that  fact so location of you are not bad from so here  
4397.21 -> I have given everything very clearly so first you  new item toward the name of the project freestyle  
4403.21 -> project okay then go to build section so that take  is equal to windows batch command and specify path  
4409.45 -> of your ahmedabad files along with the random  artful meme so first entity will be CDU our  
4415.06 -> location of your project and then run that bad so  these do things we need to specify now let us go  
4421.72 -> here see me right so say D where is our project  location this is the location right so the same  
4429.22 -> commands this is the command this is the location  and in this location my granddad batch for this  
4434.83 -> present right so we have to just paste by the name  of the fact run backpack there's only two entries  
4441.52 -> now apply and say so again it will go to this is  your project - - for specific to project again if  
4450.97 -> you go to back to dashboard it will show you all  the projects so all the projects if you want to  
4456.13 -> go specific to your project to dashboard and you  can see one entry for your project so we see here  
4462.91 -> somewhere it should be there 0 0 v1 given right  so this is a one so still we haven't run this so  
4470.8 -> the reason is giving a greater so rent means it is  failed on grey means it is not yet executed blue  
4477.97 -> means it is passed okay so it is not at executed  but if I click on this link it will go to your  
4483.79 -> your specific project dashboard so we can run in  many places we can run from here or we can also  
4490.9 -> run from the main dashboard so from here also we  can just click on this triangle click on the build  
4496.09 -> now option or we can also click on here this is  an option we have ok multiple places we have so  
4502.18 -> normally we will run on project - - is just direct  to go to your branch put here just you need to  
4509.11 -> click on the build now option so this is option  now dreams now internet will eggs good run not bad  
4514.81 -> for so I'm just licking one bill now so here we  cannot see any UI because everything is a seamless  
4519.55 -> now click on bill now so once you click on the  bill now so here you can see started execution  
4527.77 -> so just click on this progress bar just click on  this progress bar then you will see some log files  
4534.1 -> so I have just click on this progress bar now  we can see the logs are creating here so now my  
4542.11 -> project is star the same commands have executed  see now so it started my execution first time  
4547.84 -> it will take some time but from the second round  or worse it will do very faster so now we cannot  
4555.61 -> see Ami's greens everything is a seamless but the  log message you can see now you can see tests have  
4562.09 -> started so by reading this log messages we can  understand what is happening at the packet so in  
4568.42 -> the DevOps environment our test cases will run in  the same manner okay so they don't want to see any  
4575.2 -> us just they want our test case a passed or failed  does it so now we can see the read messages based  
4582.67 -> on the log messages we can easily understand  so that's the reason we have to write the more  
4587.11 -> number of blocks in the test case at the time of  writing your test case itself in detail messages  
4592.48 -> the run time it will be very very easy to debug  the issues so loss will be very useful at the time  
4599.92 -> of debugging issues now you can see so adding new  customer is also execution is done execution is  
4606.52 -> happening here so it will go faster and we can't  see any UI here everything is seamless or headless  
4613.84 -> so now everything is done now build a structures  so now I am able to execute our test cases under  
4621.97 -> bad fell within the Jenkins using freestyle  project so in the Jenkins itself we have a  
4627.88 -> two approaches one is using free state project you  can execute our test cases here we have to use run  
4634.24 -> bad fight and the second sale is second with maven  project using me one project within the Jenkins we  
4641.23 -> can use but here we need a palm dot XML so I will  also show you the second approach so let's go and  
4649.87 -> see so once we have executed build a successful  then go back to you back to your project now again  
4657.55 -> go back to your dashboard now we can see this is  torn into blue color but is successful and you can  
4665.11 -> run the same project any number of times you don't  create these multiple projects every time okay  
4669.46 -> this is only a one time job so once you created  this entry that's it so automatically test cases  
4674.89 -> will execute every time but this configuration  should not change once we have done for it this  
4681.13 -> is a one way of executing run dot bat file but we  don't follow this up this is only for practicing  
4687.01 -> purpose so we'll see the second approach maven  project how to run your test cases using maven  
4692.65 -> project so to run you a test cases using maven  crosser and Jenkins maven project you have to do  
4699.1 -> certain settings within the Jenkins itself you  have to make sure that very very important step  
4703.42 -> if you miss this step you cannot exit so when I  create a new project new item this is the maven  
4710.02 -> project so first method we already seen so here we  have used run dot bat file so here maven project I  
4716.68 -> am taking so if you want to take this maven  project we can run the bounded XML directly  
4721.48 -> through Jenkins but only thing is we need to add  a special plugins to use this Butler maven project  
4728.89 -> so how do I add those brackets so not a plugins we  need to set proper paths because maven plugins we  
4735.52 -> already executed we have already installed earlier  right so the node is in the previous screen so you  
4740.65 -> may month like is for Jing is we already installed  so now we don't need to do anything else only  
4745.27 -> thing is we have to point to your second class  because Java home so when I told you these paths  
4750.49 -> should be confident before coming here so Java  home path should be specified so when we have  
4756.73 -> to specify here is just go to Jenkins and here  managing is all the configurations done will be  
4765.4 -> done in the main and Jenkins click on this man is  Jenkins now go to global tool configuration global  
4774.58 -> to configuration but our Jenkins should know  wherever even in Java is there that's the main  
4780.23 -> important okay so the global tools configuration  so you can see JDK folder so once you click on  
4787.31 -> this JDK installations so I already configured  my JDK is this one but in your case you don't see  
4794.42 -> anything here so just use some name here called  my JDK or something else and here provide your JDK  
4800.96 -> path means your Java path so once you are provided  here don't do any option in delivery key or adds  
4806.81 -> a detail you will see some options here don't do  anything just specify the JDK name give the Java  
4813.02 -> at home so when a providing this value here Java  underscore home oh okay so once we have provided  
4818.84 -> this then directly come down apply and say and  don't do anything else okay so this is very very  
4827.39 -> important so just add my JDK provide this location  and diet so apply and save so I already done this  
4835.07 -> so I have given the screenshot also here so go to  dashboard managing means global tool configuration  
4840.32 -> go to JDK section over some name provide about  JDK part click on save and nothing this is the  
4846.95 -> configuration so now we will able to use a next  option there isn't may one option so now come  
4854.57 -> back to your dashboard now I'm taking a new item  and this time I am going to use maven project okay  
4861.11 -> so now I am giving so previously what is the name  I have given no commerce 0 0 1 something right so  
4869.36 -> 0 1 0 0 yes this is Annie may have given earlier  now this time the same version of the project but  
4879.77 -> this time I'm taking maven project this is a  neighbor project I'm just changing the name ok  
4886.25 -> same project I'm just using maven project approach  so select this maven project this time and ok now  
4896.3 -> it will go to build sections go to configuration  page yes this is your configuration page so now  
4903.2 -> what we have to do here is just directly come to  build section and this time it will show you palm  
4910.28 -> dot XML so we how to give the complete path of  your palm reading sermon so where is your pounded  
4917.06 -> XML is present in your project from very right  so this is a location you have to specify this  
4924.59 -> is the complete location here to you so in this  particular location your palm read example is  
4929.66 -> present so what is the command we have to execute  here the command is clean install clean install  
4937.82 -> whatever command we have executed in the command  grande the same clean install MV and we don't  
4943.25 -> require ambient by default will be taken care by  a mere member so just specify the location of your  
4948.68 -> palm under this route palm directory and goals and  options is a maven command a clean install that's  
4955.94 -> it so once we added this then apply and save so  again it will enter into the project dashboard  
4963.32 -> so from here you can draw any more concept now  I am going to run this one more time so click  
4968.33 -> on bail it now so once you click on the build now  it is started execution so again you pick lick on  
4974.24 -> this progress bar just click on this progress  bar you will see the log files so all the log  
4979.88 -> messages you can see here this is another approach  so these are the two approaches we have to swallow  
4986.96 -> to execute your project within the Jenkins so  it is started so first time it will take some  
4995.84 -> time because now it is starting so there are a  lot of things are there so case you have to go  
5006.58 -> step by step spend some time on this do very  slowly don't be naughty buddy so please do  
5012.43 -> step by step very slowly and understand the step  and boot and make use of this PDF ll say I will  
5018.58 -> share this presentation today so go through each  and every screen and do the exactly the same way  
5023.92 -> and if you miss anything if you do something  wrong you get it very very difficult to fix  
5029.53 -> it okay so please do carefully so now my test  case is running customer details is providing
5041.689 -> okay so once it is done you will get the bill  success here test is passed and finally you will  
5048.2 -> see build success so we are able to also integrate  our test cases using maven project within the  
5054.08 -> whirring within your watching it snow build is  success till the diversity will exude our test  
5059.87 -> cases in this Butler okay so this approach they  will pause so this configuration we have to do as  
5066.169 -> a QA first time okay and DevOps team automatically  excuse the same project multiple times I will go  
5072.29 -> to your project now my project is successful so  this is the maven project is successful okay so  
5079.13 -> just go through these patellas keys and do as  it is so now what we have seen so far it is  
5085.07 -> we have just executed our complete project using  freestyle project using Thunderbird file and also  
5091.729 -> variable takes good over complete project using  maven project that is for Maddux ok these are  
5096.95 -> very very important so for today just practice  all these things till here this is very very  
5101.9 -> important and tomorrow I will show you few more  things in Jenkins ok but here in this particular  
5108.2 -> approach is there is some problem so let me just  also give that butter problem so tomorrow show  
5114.14 -> it again so as I said here there is a QA team  and here the dev team is there ok so here the  
5121.82 -> dev ops team is there so where is our Jenkins  is running here our Jenkins is present here the  
5128.18 -> Jenkins is installed so they have given just URL  to you but the Jenkins is not there in your local  
5134.27 -> system right so Jenkins you will automatically ok  so Jenkins is located in diversion one not in your  
5142.25 -> environment but in today's session what we have  done we have Jenkins installing our Q environment  
5148.34 -> our local system so we are able to configure  paths even pom dat xml path also have a given  
5154.729 -> my local system path because all my project is  completely available in my local system so the  
5160.64 -> jig is also there in the same system project and  Jenkins both are present in the same location so  
5166.22 -> that I can easily configure all the paths within  the Jenkins I should able to execute it successful  
5171.2 -> there is no issue at all but in the real time you  don't do this approach because you don't keep any  
5178.05 -> files in your local why because Jenkins will be  installing develops a system they will guess just  
5183.84 -> share the URL with you but uh actual application  is airing develops a server right but your project  
5190.11 -> is still there in your local system but how  we will configure your local path in remote  
5194.58 -> Jenkins right this is an issue where how we can  configure your local path in your Jenkins because  
5201.27 -> Jenkins is a remote application which is there  in the DevOps machine or develops a server but  
5206.04 -> your project is located in your local system  so da here the biggest problem so there are  
5212.37 -> two solutions one solution is we can just move  the complete project in the dev server or DevOps  
5219.51 -> machine and there we can configure the local parts  that's the one approach but these occurs will will  
5225.479 -> not following the real term because there are so  many people are working on so many things so how  
5231.33 -> we can integrate all these projects and how we  can send them to devups it is a small company  
5236.25 -> were not open full of working that is fine but in  the real time it doesn't happen like this so this  
5241.59 -> is the conflict we have but how we can overcome  this so we have to use a common repository called  
5248.4 -> git and github repositories so tomorrow we are  going to discuss about this so we will put all  
5255.36 -> the code in get and we drop repository right so  this get done get repository code can be accessed  
5261.959 -> through URL so Jenkins will take the our code  from the git and github repository so this is a  
5268.68 -> common location where we have to keep all our code  a project coding to this one we have to check in  
5274.32 -> all our code into jatin jit repositories from  there Jenkins will take it every day and this  
5280.65 -> will automatically execute so in this particular  content we have to just configure github URL in  
5286.47 -> the Jenkins we don't provide any local paths  so by using this approach we can overcome that  
5292.35 -> particular conflict ok so tomorrow we'll discuss  more about this JIT what is JIT what is G table  
5297.99 -> how we can check in our code in the git and github  repositories how Jenkins will take that code all  
5303.45 -> these things we will discuss in to Mohnish okay  so I will stop here so you get understood right  
5310.13 -> so far so this is very very important and if  you put any two or three years of experience  
5315.8 -> then you can easily answer the questions if you  know this but you are propping and 90% of the  
5321.53 -> people don't teach these kind of topics so this  is very hundred percent real genuine topics so  
5327.68 -> please understand and follow the same thing  and if you get any questions any real-time  
5332.18 -> questions you will easily understand and it  can easily answer those questions ok guys so  
5338.24 -> I'll stop it here guys so rest of the things  so we'll have these skills in tomorrow session

Source: https://www.youtube.com/watch?v=F8Nfjwneeb4