Jenkins in Tamil-01-Continous Integration in Tamil |Jenkins beginners in Tamil with English subtitle
Jenkins in Tamil-01-Continous Integration in Tamil |Jenkins beginners in Tamil with English subtitle
#jenkins #devops #ci_cd #tamiltutera #devops_in_tamil
Jenkins in Tamil-01-Continous Integration in Tamil |Jenkins beginners in Tamil with English subtitle
• Jenkins in Tamil-01-Continous Integra…
Site: https://tamiltutera.com
Telegram Link: https://t.me/tamiltutera
Youtube Channel: / tamiltutera
Blog: https://tamiltutera.blogspot.com/
Like Facebook Page : https://www.facebook.com/tamiltutera
Follow us on Twitter: https://twitter.com/tamiltutera
Blog : https://tamiltutera.blogspot.com
TamilTutEra - Ansible in Tamil | Ansible in தமிழ் (Tamil) | Ansible Tutorial for beginners in Tamil | Ansible Tutorial in Devops | ansible playbook
• TamilTutEra - Ansible in Tamil | Ans…
TamilTutEra-Docker in Tamil | Docker for Beginners in Tamil | Docker | Docker DevOps Tutorial in Tamil | DevOps Tutorial in Tamil
• TamilTutEra-Docker in Tamil | Docker …
TamilTutEra - Ansible Tower in Tamil | Ansible in தமிழ் (Tamil) | Ansible Tower Tutorial for beginners in Tamil | DevOps Tools in Tamil | Cloud
• TamilTutEra - Ansible Tower in Tamil…
#tamiltutera,
#devops,#tamil_tech_tutorials,#tamil_devops,#devops_in_tamil,
#docker_in_tamil,#ansible_in_tamil,#git_in_tamil,
#vagrant_in_tamil,#jenkins_in_tamil,
#automation_in_tamil,#tamil_tut_era,#it_automation_in_tamil,
#automation,#infrastructure_automation,#install_jenkins_in_centos,
#jenkins_installation_in_centos,#jenkins_installation_in_tamil
Content
0.16 -> Hi guys, welcome to Tamil Tutera
2 -> Today we are going to see Jenkins
5 -> So, all the videos will be about Jenkins
9 -> First, you will remember Jenkins as CI and CD
13 -> CI means Continuous Integration
15 -> CD means Continuous Delivery or Deployment
18 -> So, we are going to see Continuous Integration
25 -> So, let's see overview of Continuous Integration
28 -> So, first we are going to see what is Continuous Integration
32 -> Continuous Integration is a development practice
35 -> So, what developers do is
37 -> Daily, they develop code in their source code
42 -> So, for every code changes or new code models or issue bugs
49 -> So, what they do frequently is
52 -> They will be committing code in shared repository
55 -> So, for every commit changes or new code models or issue bugs
61 -> So, what they do is
64 -> Teams can detect every problem in your source code
71 -> So, teams can track and fix bugs easily
76 -> So, this is a practice of Continuous Integration code changes
81 -> So, you can continuously integrate code changes in your Git or
90.167 -> Bitpocket
91 -> So, next is
92 -> A project can be built and compiled easily
96 -> So, source code in a cloud
99 -> So, since it is permanent, there is no problem
105 -> So, the code will be built and compiled correctly
108 -> So, next is ensure that any changes pass all tests
111 -> So, you can easily ensure all tests, guidelines, code compliance
117.364 -> standards
118 -> Because teams follow each other, there will be issues and bugs
123 -> So, it is very useful to see that no one can re-edit the code
128.6 -> and no one can crash it
131 -> So, what are the benefits of Continuous Integration in server
135.546 -> development
136 -> So, you can easily catch an issue
138 -> Before it occurs, it is a big issue
142 -> So, it is a big benefit in server development
146 -> And then, everyone can see what is happening in code changes
150 -> Who fixes the code bug
152 -> Who commits the code
155 -> You can easily underline what is happening in server development
160 -> Continuous integration is very useful for building and automating
164 -> Continuous integration is very useful for continuous deployment
170 -> Continuous integration plays a big role in delivering the service
177.273 -> easily
178 -> Continuous integration tool is used in Jenkins
183 -> There are thousands of plugins for continuous integration
189 -> Jenkins supports continuous integration plugins
196 -> So, let's see how continuous integration process was before
203 -> Developers will commit the source code and then the integration
210.143 -> build will take place
213 -> QA team will do testing and validation
219 -> After validation, they will check for bugs
224 -> If there are bugs, the mail will be triggered and will go to
229.571 -> developers
230 -> They will manually check the mail and fix the bugs
235 -> They will change the source code and do it again
238 -> If validation is successful, the software will be released successfully
243 -> QA testing will be done manually
248 -> After completing the complete cycle, the bugs will be fixed and
251.667 -> the mail will be triggered and will go to developers
255 -> After completing the complete cycle, developers will wait
260 -> Developers will wait for the QA team to be successful
266 -> Until the application is successfully deployed
269 -> Continuous integration is before process
272 -> Drawbacks are no constant feedback
277 -> Developers have to wait till the application is deployed until
281.615 -> QA team verifies
283 -> Bug fixing cost is high
285 -> It takes a lot of time and process
288 -> QA team will verify the mail and then the developers will verify
294 -> and then analyze and then fix
297 -> Slow software delivery
300 -> It takes a lot of time and process
303 -> It will be inconsistent
305 -> They will be stuck in the process without a proper success rate
312 -> It will take a long time and process
318 -> Before process is drawbacks
321 -> How to overcome this process
324 -> Developers will frequently check in
328 -> What is happening in the source code
330 -> What code changes
332 -> Build will happen after changes
335 -> Testing will be done after the build
338 -> After deployment, they will check for changes in the source code
344 -> Build will happen after changes
348 -> Build will happen and test changes
350 -> After testing, they will deploy in test or development
355 -> After deployment, they will check for changes
358 -> If there are no changes, it means it has been successfully deployed
362 -> What are the continuous integration server plugins you use
366 -> Jenkins will show you the success rate
372 -> Once the testing is successful
377 -> They will release the software
379 -> If the software release is successful
382 -> Developers will get a success or failure mail
386 -> Before releasing the software, you fix the bugs
396 -> After that, you test in the actual environment
402 -> After that, you release the software
404 -> You can fix bugs instantly and constantly
408 -> That is the big advantage
410 -> Let's see the benefits
412 -> Constantly feedback for developers
417 -> Because of automated build and test process
422 -> Bug fixing time is reduced drastically
430 -> Fast software delivery
432 -> Because of automated build and test process
436 -> You can fix bugs easily and release frequently
442 -> These are the benefits of continuous integration
448 -> I hope you like this video
450 -> If you like this video, like, comment and subscribe
453 -> Click the bell icon to get notifications
[Powered By Dubverse]
Source: https://www.youtube.com/watch?v=jjVUaBsWMJs