This document summarizes a workshop presentation on using Jenkins for continuous integration. The presentation covered what Jenkins is and how it can be used to automate the software build process. It explained the basic CI process and how to configure a Jenkins job to fetch code from Git, build and test a project, generate Cucumber reports, and send email notifications. The goal was to demonstrate setting up a sample Jenkins project that builds an automation test suite from source control, runs the tests, and reports results.

1. Occasion:
Date:
Present:
Classification:
Meet Jenkins
- everyone's favourite butler -
ISTC Workshop
31-10-2015
Ariciuc Răzvan
Public

2. 2
● What is Jenkins
● What is a CI process
● How to create a job in Jenkins
● How to add parameters to a job
● How to configure e-mail notification
● How to integrate Git in a Jenkins jos
● How to generate Cucumber reports for a job
Agenda

3. 3
● What is Jenkins ?
o Jenkins is an open source continuous integration tool.
o Jenkins provides continuous integration services for software
development.
● What is it used for ?
o Jenkins is used for automating a software's build process.
o Jenkins is used for running automation tests against build.
o Jenkins is used for gathering test reports and metrics from a software
product.
● Who uses it ?
o Jenkins is by everyone.
Introduction

4. 4
The CI Process

5. 5
The Dashboard
View
Build machines &
executors
Job (Project)
Runing Job

6. 6
The Job Interface
Reports
Build (start)
Build history
Configure

7. 7
● Jenkins server has to be pre-configured with
• Git
• JDK
• E-mail server
• Maven
• Git credentials
• Jenkins slaves
• Jenkins security
• Cucumber reports
• Browsers (Chrome,Firefox)
● Most of these are done by adding plugins to Jenkins
Notes
Since this presentation was in support of a workshop the following need to be take into consideration
o These configurations are not covered by the presentation
o The project used in the 2’nd part of the presentation is no longer on GitHub
Jenkins pre-requisites

8. 8
Creating a Job

9. 9
Add a Build Step
3 Build

10. 10
Run the Job
3 Build
4 Test

11. 11
Add Build Parameters

12. 12
Configure Email Notification
6 Notify Success of Failure

13. 13
Configure Email Notification
6 Notify Success of Failure

14. 14
Coffe Break

15. 15
Add Repository
2 Fetch changes

16. 16
Aditional Repository Settings

17. 17
Update Build Command
3 Build

18. 18
Add Reports
5 Reports

19. 19
Read Reports
5 Reports

20. 20
● We have create a Jenkins job (project) that
• Fetches the latest changes from a SCM system (Git)
• Builds the project (complies the automation test files)
• Runs tests ( executes the automation test)
• Generates Cucumber reports
• Sends an e-mail in case of failure
• Keeps history of previous job runs (builds)
Summary

21. 21
Q&A
Contact
Presenter Ariciuc Razvan
E-mail ariciuc.razvan@yahoo.com
Q&A