Jenkins is an open source tool that automates the continuous integration process. It monitors source code repositories for changes, automatically builds the code, runs tests, and provides feedback to developers. Before CI tools like Jenkins, software delivery was slow and locating bugs after integration was difficult. With Jenkins, every code change triggers an automatic build and test, improving feedback and release frequency while reducing bug fixing time. Jenkins has over 1000 plugins and alternatives include Travis CI, Buildbot, Bamboo, and JetBrains TeamCity.

1. 1 December 2017 www.snipe.co.in 1
SNIPE TEAM
129 November 2017

2. 2
Jenkins – CI :-
29 November 2017

3. 29 November 2017 3
Contents:-
o What is Jenkins?
o How It works?
o Process Before CI
o Problems Before CI
o Process After CI
o Alternatives of Jenkins
o Jenkins Plugins

4. 4
o It is a Continuous Integration Server.
o It is an Open Source Tool.
o It is written in Java.
o It has over 1000+ Plug-ins which makes it widely
accepted tool for CI.
What is Jenkins ?
29 November 2017

5. 5
o Notice a Change
o Check out the Source Code
o Execute the build tests
o Record and Publish results
o Notify Developers
How it Works ?
29 November 2017

6. 6
o Group of developers make changes to the Source
code that is present in Source code repository.
( Source code repository may be Git, Subversion
etc)
Process Before CI :-
29 November 2017

7. 7
o When the code is written in the repository it will be build
by tools like Ant, Maven etc.
o The build application is then sent for testing, if they find
a bug they will notify the developer.
o If there are no bugs it will be sent for production server
for release.
29 November 2017

8. 8
o Developers have to wait till the complete software is
developed for the test result.
o If it fails, locating and fixing bugs is very difficult.
o Developer need to check the entire code of the
software for bugs.
Problems Before CI :-
29 November 2017

9. o Software delivery process was slow.
o Continuous feedback relating to coding, build failures
and test status were not available.
929 November 2017

10. 10
o After every change to the source code an auto build is
triggered and is automatically deployed on the test server.
29 November 2017
Process after CI :-

11. o If the test result shows any bug in the code the
developer have to check the last change made to the
code.
o This Increases the frequency of new software
release.
o The Concerned teams are notified with feedback.
1129 November 2017

12. 12
o Travis CI
o Buildbot
o Bamboo
o JetBrains TeamCity
12
Alternatives to Jenkins :-
29 November 2017

13. o Build Tools
13
• Ant
• Maven
• MSbuild
• Cmake
• Gradle
o Test Frameworks
• Junit
• Nunit
• MSTest
• Selenium
• Fitnesse
Jenkins Plugins :-
29 November 2017

14. 14
• Thank You
29 November 2017