Jenkins in Tamil-02- Continuous Delivery in Tamil | Jenkins beginners in Tamil with English subtitle
Jenkins in Tamil-02- Continuous Delivery in Tamil | Jenkins beginners in Tamil with English subtitle
#jenkins #devops #ci_cd #tamiltutera
Jenkins in Tamil-02-Overview of Continuous Delivery in Tamil | Jenkins beginners in Tamil | CI\u0026CD |
Jenkins in Tamil-02- Continuous Delivery in Tamil | Jenkins beginners in Tamil with English subtitle | DevOps | Jenkins
• Jenkins in Tamil-02- Continuous Deliv…
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
Jenkins for Beginners in Tamil-01-Overview of Continous Integration in Tamil |Jenkins beginners in Tamil | Jenkins
• Jenkins in Tamil-01-Continous Integra…
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.008 -> Hi guys, welcome to Tamil Tutera.
2 -> The video we are going to watch is overview of continuous delivery.
5 -> So, what is continuous delivery?
8 -> So, continuous delivery is a way to deploy an application.
13 -> There are many ways an application can be deployed.
18 -> There are many manual steps and many way principles to follow.
23 -> The most traditional way to follow is very slow.
28 -> DevOps Agile methodologies are used to promote code.
33 -> So, the code you develop is used to deploy on the production
40.385 -> server.
41 -> DevOps Agile methodologies are used to promote code.
45 -> So, the code promotion and deployment process is done through
53.333 -> continuous integration.
55 -> So, the application moves continuously.
59 -> So, continuous pipeline, continuous code promotion and deployment
65.667 -> process is done automatically.
69 -> So, that is called continuous delivery.
72 -> So, next I will explain about continuous deployment.
85 -> So, pipeline refers to each promotion stage an application takes
89.667 -> while it is being developed.
92 -> So, when you are delivering a pipeline, there is a promotion
101.167 -> stage.
102 -> So, the code is built, tested and then delivered to the development
105.692 -> server.
106 -> And then, the code is delivered to the test server.
109 -> So, after the unit testing and acceptance testing is done, the
114.177 -> code is moved to production ready.
117 -> So, a continuous pipeline is created.
120 -> So, continuous integration is to constantly integrate the code
127.615 -> changes in a pipeline.
131 -> So, next logical step is to make sure that the code is ready
137.067 -> for production.
138 -> So, the test is passed and the acceptance testing is done.
147 -> So, the next stage is continuous deployment.
155 -> So, the code is ready for production and then the next step is
159.062 -> to automatically deploy.
160 -> So, that is called continuous deployment.
162 -> So, this is a continuous pipeline where you are developing the
166.583 -> code.
167 -> You are committing each code and the changes are being integrated.
172 -> So, the integration is done and the unit testing, acceptance
175.75 -> testing and load testing is done.
178 -> So, the next logical step is to make sure that the code is ready
182.375 -> for production.
183 -> So, the next logical step is to make sure that the code is ready
186.5 -> for production.
187 -> So, this is a continuous deployment pipeline.
191 -> So, this is a continuous deployment pipeline.
195 -> So, the developers are committed to the code changes.
201 -> So, the code is built and then the CI Jenkins, UTID, unit testing
208.222 -> and integration testing is done.
211 -> So, acceptance testing and load testing is done in a test environment.
215 -> So, acceptance testing and load testing is the continuous delivery.
221 -> And then when the production is ready, it is called continuous
224.667 -> deployment.
225 -> So, this is the continuous delivery pipeline.
227 -> So, this is how your Jenkins pipeline or Agile methodology pipeline
231.714 -> will look like.
233 -> So, this is the continuous deployment and then delivery pipeline.
239 -> So, next we will see what are the advantages of continuous delivery
243.235 -> and what can be done.
245 -> Automation is the most important thing for DevOps code formation.
249 -> Everything is automated. There is no manual intervention or manual
252.636 -> steps.
253 -> So, the manual steps are used to overcome errors and problems
259.188 -> in continuous delivery and deployment.
262 -> So, almost everything is manual and everything is automated.
267 -> And then unit testing and everything is done automatically in
272 -> continuous delivery.
273 -> And then in continuous delivery, a variety of DevOps tools are
276.667 -> used.
277 -> So, there are a lot of DevOps tools.
279 -> So, we will see all the videos in the next video.
283 -> So, one of the tools in Git is Git repository.
289 -> It does all the application codes.
291 -> So, Selenium is used for automated testing.
294 -> So, SonarQube is used for quality of the results.
296 -> So, you can review how successful it is in automation testing.
302 -> So, our continuous integration tool is Jenkins.
306 -> You can easily deploy using the pipeline.
310 -> So, the benefits of continuous delivery are
314 -> Immediate bug detection and automated software releases.
319 -> So, you can automate and deploy all the deliveries.
324 -> So, the productivity of the operators and developers will increase.
333 -> So, the developers can check the code successfully.
343 -> So, the manual effect will be reduced.
346 -> And then the developers will increase productivity.
349 -> And then deployable system at any given point.
353 -> So, continuous delivery means that the code will be deployed
356.846 -> at any time.
358 -> In production, test server or development server.
361 -> So, the record of evolution will be increased.
366 -> So, the detect system development problems earlier.
370 -> So, if you detect any problem in the development,
375 -> it will be detected very quickly.
378 -> So, the code release will be detected quickly.
384 -> It will be useful for you to solve and move to production.
388 -> And then reduce the risk of cost and then schedule on budget.
391 -> So, it will save time.
393 -> So, it will save production.
395 -> And then you can schedule continuous delivery.
398 -> If you schedule it, it will save cost.
402 -> So, you can finish the delivery within the budget.
405 -> So, without taking much time.
407 -> So, next is measurable and then visible code quality.
411 -> So, your code quality can be reviewed.
414 -> How is the code quality?
415 -> How is the code standard?
416 -> How much success rate will it give?
418 -> How does the code run?
420 -> So, you can continuously deliver your application code with the
424.167 -> code quality.
425 -> So, this is overview of continuous integration and development.
430 -> So, as I said earlier, your development code is in the SAD repository.
437 -> So, how to verify the integration?
439 -> Automated built-in automated tests will verify the integration.
443 -> Whether it is successful or not.
445 -> So, one of the key benefits is that you can easily detect errors.
455 -> And then it will be very useful and easy to fix.
459 -> And then continuous deployment and continuous delivery is the
462.75 -> best practice developed.
464 -> For keeping your application deployable at any point.
467 -> So, your application will be useful to deploy your code at any
474.385 -> time.
475 -> So, this is the continuous delivery deployment video.
479 -> I hope you like this video.
480 -> If you like it, please like, comment and subscribe.
482 -> Don't forget to click the bell button.
[Powered By Dubverse]
Source: https://www.youtube.com/watch?v=e-FwhW-B9Gc