DevOps Training | DevOps Online Training

1. What is Jenkins? +91-9989971070 www.visualpath.in

2. What is Jenkins? • Jenkins is an open source automation tool written in Java with plugins built for Continuous Integration purpose. • Jenkins is used to build and test your software projects continuously making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. • Before coming to our main topic of discussion ‘What is Jenkins?,’ let’s begin this Jenkins tutorial with an introduction to continuous integration. www.visualpath.in

3. What is Continuous Integration? • Continuous integration (CI) happens to be one of the most vital parts of  DevOps. It is primarily used to integrate various stages of DevOps together. • In other words, it is a coding practice that essentially enables the development team to make and implement small changes in the code and version control methods quite frequently. • Continuous integration is usually done in the form where all developers push the code onto a shared repository mostly multiple times a day. www.visualpath.in

4. Continuous Integration Using

5. Why use Continuous Integration? • Reduction of integration links: All projects employ more than one person to develop and it greatly increases the risk of errors during integration. Depending on the complexity of the code, it is possible that a lot of changes would have to be made. • Here comes CI to the rescue and helps alleviate the issues as it allows for regular integration. • Higher quality of code: As the risks drastically reduce, a lot of the time and manpower can be diverted to creating a much more functionality-oriented code. • Code in version control works: Committing something that breaks the build immediately triggers a notification thereby preventing anyone from pulling a broken code. www.visualpath.in

6. Why use Continuous Integration?

7. Ease of testers: Retaining the different versions and builds of the code eases the work of QAs to understand, locate, and trace bugs efficiently. • Decreased deployment time: Automating the process of deployment eases and frees up a lot of time and manpower. • Increased confidence: The absence of a possible failure or breakdown gives developers peace of mind and thereby helps in delivering greater productivity and higher quality products. www.visualpath.in

8. Sample Use Case • Consider an existing system that is meant to create a healthcare system that pulls the code from the shared repository at a certain time every day and builds it. • This is something like CI except for the fact that it only builds once a day. This essentially leads to finding bugs only at one point of time in a day. • An alternate way to this system is to make it CI-compliant, i.e., to enable the system to push the code onto the shared repository every time a change is made to it and build it. www.visualpath.in

9. CONTACT For More Information About DevOps Online Training Address:- Flat no: 205, 2nd Floor, Nilgiri Block, Aditya Enclave, Ameerpet, Hyderabad-16 Ph No : +91-9989971070 Visit : www.visualpath.in E-Mail : online@visualpath.in

10. THANK YOU Visit: www.visualpath.in