Continuous integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day, with each check-in verified by an automated build to detect problems early. Practicing CI involves having a central code repository, automated builds for every commit that are self-testing, and the ability to fail and deploy builds fast. Jenkins is a popular open source CI server that can be used to implement CI workflows and pipelines through features like its plugin library and Jenkins Workflow that allows capturing complex pipelines in a single job.

1. Continuous Integration
Jumpstart CI with Jenkins Workflow
@udaypal
1

2. Topics
• Economics of Continuous Integration
• What is Continuous Integration?
• Practicing continuous integration
• Continuous Integration with Jenkins
• Jenkins workflow
• Q & A
2

3. About Me
• Director, Solutions Architect
• Open Source Evangelist
• Developer @ heart
• Occasional Committer
• Soccer referee
3

4. Who we are
• CloudBees Founded in 2010
• The Jenkins Enterprise Company
• Core Contributors
• Products
• Jenkins Enterprise
• Jenkins Operation Center
• Support, Training, Consulting, JUC etc..
4

5. Economics of CI
5

6. 6
Economics
Source
:
Applied
So*ware
Measurement,
Capers
Jones,
1996

7. Time
$
Developer
Computer
7
Economics

8. What is CI?
8

9. What is CI?
Continuous Integration (CI) is a development practice that
requires developers to integrate code into a shared
repository several times a day. Each check-in is then
verified by an automated build, allowing teams to detect
problems early.
By integrating regularly, you can detect errors quickly,
and locate them more easily.
9

10. Version
Control
Build &
Unit Tests
Functional
Tests
Acceptance
Tests
ReleaseDevelopment
Checkin
Trigger
Feedback
Checkin
Trigger
Feedback Trigger
Feedback
Checkin
Trigger
Feedback Trigger
Feedback
Feedback
Approved
Approved
10

11. Practicing CI
11

12. Continuous Integration
Practicing
Continuous
Integration
• Central Repository
• Build every commit
• Automate builds
• Builds are self-testing
• Fail fast, build fast
• Test in production clone
• Automate deployment(s)
• Analyze
12
Change'
Build'
Test'Deploy'
Analyze'

13. Continuous Integration
Team
Responsibilities
• Commit Early, commit often
• Never commit broken, untested code
• Broken builds are the highest priority
• Don’t checkin when build is broken
• Make sure last checkin of day doesn’t break build
13

14. Jenkins and CI
14

15. Jenkins
• 1000
• 597
• 70
• 8
• 1
15
- Over 1000 Plugin
- Over 500+ weekly releases
- 70% Market
- 8+ Years
- #1 CI Server

16. Jenkins
16
What type of tasks do you use Jenkins for?
Build
Test
Code Analysis
Batch Tasks
Release
Operations
Deployment
Other
0% 25% 50% 75% 100%
5.37%
47.81%
14.95%
48.37%
38.47%
64.07%
86.42%
95.19%

17. Jenkins
Hub
Of
Continuous
Delivery
17
Binaries
Code
Analysis
SCM Production
Functional
Tests
Perf / Load
Test

18. Jenkins CI
Old
Workflows
• Copy Artifacts
• Build Triggers
• Build Flow
• Build Pipeline
• Build Delivery Pipeline
18

19. Jenkins CI
Complex
Job
Chaining
• Many atomic jobs
• Mix build triggers, parameterized build …
• Limited logic
• Hard to share variables / state between jobs
• Cannot survive restart
• Disjointed views & configuration sprawl
19

20. Jenkins Workflow
Features
• One job to capture complex pipeline
• Based on Groovy
• Can survive restarts
• Throttle builds
• Human input
• Visualization
20

21. Summary
• CI is cost effective
• CI reduces manual error prone processes
• CI enables better visibility
• CI establishes greater confidence
• CI is a necessary step towards CD
• Jenkins is awesome @ CI
21

22. 22