Jenkins in Tamil-03-Introduction Jenkins in Tamil | Jenkins for beginners in tamil | CI&CD |DevOps
Jenkins in Tamil-03-Introduction Jenkins in Tamil | Jenkins for beginners in tamil | CI&CD |DevOps
#jenkins #ci_cd #devops #tamiltutera
Jenkins for Beginners in Tamil-03-Introduction Jenkins in Tamil | Jenkins for beginners in tamil | CI\u0026CD |DevOps
• Jenkins in Tamil-03-Introduction Jenk…
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-02-Overview of Continuous Delivery in Tamil | Jenkins beginners in Tamil | Jenkins
• Jenkins in Tamil-02- Continuous Deliv…
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.127 -> Hi guys, welcome to Tamil Tutera. Today's video is about Jenkins.
4 -> Let's see a brief introduction about Jenkins.
6 -> First, we are going to see what is Jenkins.
11 -> Jenkins is a leading open source continuous integration tool.
15 -> Jenkins was developed by the Sun Microsystems team at Accent
21.364 -> Creation.
22 -> They started the project in the summer of 2004.
26 -> Jenkins is used to build, test and monitor a software continuously.
33 -> It is used to view the remote job status and to check whether
38.85 -> the software is being delivered or not.
42 -> This tool is very useful for that.
44 -> It is very easy for the developer teams to maintain their latest
57.714 -> stable code.
60 -> Jenkins is easy to integrate with other tools.
77 -> Core Jenkins is easy to handle and understandable.
83 -> Jenkins is run on a schedule.
91 -> It is run on a schedule and triggering events.
100 -> We are going to see how to configure the pipeline in the next
105.571 -> video.
106 -> Jenkins is a simple and manageable pipeline.
116 -> You can configure the pipeline in Jenkins.
145 -> Let's see what is CICD with Jenkins.
148 -> Developers frequently check the code in the source code deposit.
156 -> Once you commit the source code in the master, Jenkins will configure
161.333 -> it in the continuous integration server.
164 -> Jenkins will build the source code and test it in the test and
169.2 -> development cell.
170 -> Then, it will be deployed.
172 -> Once the code is deployed, it will be tested and if there are
177.652 -> any issues, it will be sent to the source code.
182 -> The developers will get a revision notification and then they
188.25 -> will build and test it again.
192 -> Once the build and test is completed, Jenkins will check the
200.462 -> code again.
202 -> Jenkins is easy to deliver and deliver without any delay.
212 -> It is a time-saving and cost-saving solution.
222 -> It is an automated solution.
228 -> Once the test is successful, Jenkins will release the software.
233 -> Once the software is released, the developers will get a mail
242.167 -> notification.
243 -> Once the mail notification is sent, the developers will check
246.571 -> the source code again.
248 -> Once the test is successful, the developers will finish the test
251.929 -> and complete it.
253 -> This is the simple architecture of CICD with Jenkins.
258 -> It is an open source tool.
263 -> It is easy to install and configure.
268 -> It is a single-click solution.
273 -> It is a single-click solution.
278 -> It is a rich plugin ecosystem.
283 -> It has thousands of plugins.
288 -> It has thousands of plugins.
293 -> It has thousands of plugins.
298 -> You can easily import and install plugins.
303 -> You can easily import and install plugins.
308 -> You can easily import and install plugins.
313 -> You can easily import and install plugins.
318 -> This is a feature that can be used for multiple remote systems.
323 -> This is a feature that can be used for multiple remote systems.
328 -> you can manage your jobs, schedule, dispatch, execute remote
334.231 -> jobs in distributed environment
337 -> you can easily manage using Jenkins
340 -> this is the features of Jenkins
345 -> so distributed architecture means
347 -> Jenkins and master are the installation nodes
350 -> this is the control node
352 -> this is the main Jenkins master server
354 -> you can install Jenkins
356 -> you can add slaves to the machines you are going to install
366 -> slaves is nothing but node machine
369 -> you can mean both node and slave
372 -> this machines are either windows, macOS, Linux, Unix, storage,
379.364 -> terminal windows
381 -> this is definitely agent based
383 -> so you need to have an agent in the slave and node machine
390 -> so your job execution and status will be returned to master
401 -> so you can easily manage your jobs, dispatch, monitor slaves
407.25 -> and see if they are successful
411 -> you can see the job results in Jenkins master
417 -> you can see which jobs are successful and which are not
421 -> you can directly execute a job in Jenkins master and slave machines
427 -> master instance will handle all requests
432 -> each slave is running as an independent entity
440 -> so each request is running as a multi-processing and multi-threading
447 -> so in each node slave, you can execute 50 to 100 concurrent jobs
457 -> so you can run parallel jobs
460 -> so it will save time
462 -> so this is the distributed architecture of Jenkins
466 -> so what is the usage of Jenkins for developer
471 -> you can install Jenkins.var file
473 -> so you can install the var file by typing java-ja Jenkins.var
477 -> so it will be easy to install
480 -> so you can check out a new job in a new project
485 -> you can watch the check-in stages and revisions
489 -> you can create a new job and add it to the pipeline
493 -> you can easily fix the errors and test it
497 -> there is multi-technology support
499 -> not only for PowerShell, Crypto, T, Cloud and Dots
505 -> there is a simple programming language
507 -> for example C, Java, C Sharp, Python, Perl
511 -> so SQL server, SQL languages
514 -> there is multi-technology support
517 -> so you can test and build
521 -> and deploy the code
523 -> so what are the technologies used for testing
525 -> JUnit, NUnit, MSTest, Selenium
531 -> so there are 300 plugins in Jenkins
536 -> mainly for server configuration management
539 -> there are builders, test framework, virtual machine controllers,
545.222 -> notifiers
546 -> static analyzers
548 -> so each plugin has its own usage
551 -> so you can install and use it
553 -> version control system plugins are
555 -> Akira, Bajara, Git, Bitkeeper, Bitpocket
559 -> Harvest, SVN, Subversion, Team Foundation Server, SVM
566 -> Visual Show Server
568 -> so there are so many plugins available
571 -> so next is test frameworks
575 -> so there are JUnit, Selenium, MSTest, Selenium
579 -> so you can use and tools, maven, greddle, MSBuild, CMake, Grails
584 -> so you can use these tools to build
587 -> GroovyScript is used for build
591 -> Jenkins has other tools support
594 -> so as I said, it is a rich plugin ecosystem
598 -> so there are many plugins available
630 -> AWS EC2 instances, VMware
632 -> So, these are all plugins
634 -> and other tools are supported
636 -> in Jenkins, so multi languages, multi tools
638 -> so continuous integration
640 -> automated scripting
642 -> so your short development life cycle
644 -> so in an agile method
646 -> it will be very useful
648 -> for you, so easily your code
650 -> will be continuously integrated
652 -> and delivered, and to deploy it
654 -> and to manage the code
656 -> and to stable it, Jenkins is very useful
658 -> so this is Jenkins introduction
660 -> if you like this video, please like, comment and subscribe
662 -> and don't forget to click the bell button
664 -> to watch more videos
[Powered By Dubverse]
Source: https://www.youtube.com/watch?v=iRGz2pRw-VA