This presentation illustrates how Jenkins evolved from being a pure Continuous Integration Platform to a Continuous Delivery one, embracing the new design tendency where not only the build but also the release and the delivery process of the product is automated. In this scenario Jenkins becomes the orchestrator tool for all the teams/roles involved in the software lifecycle, thanks to which Development, Quality&Assurance and Operations teams can work closely together.

1. ©2015CloudBees,Inc.AllRightsReserved©2015CloudBees,Inc.AllRightsReserved
Continuous Delivery with Jenkins
Jenkins Solutions to Implement Continuous Delivery
Valentina Armenise

2. ©2015CloudBees,Inc.AllRightsReserved
Me
2
http://varmenise.tumblr.com/
Linkedin
https://github.com/var
menise
• 2 years as Java
Developer at Open
Reply
• 1 year as Developer
Success Engineer at
CloudBees
• 1 year as SA at
CloudBees
• NOW: Software
Engineer at Cloudbees

3. ©2015CloudBees,Inc.AllRightsReserved
About CloudBees
3
Who are we? CloudBees is the premier provider of Jenkins
Continuous Integration services and support
What do we
do with
Jenkins?
CloudBees optimizes Jenkins for the enterprise
• Jenkins Operations Center
• Jenkins OSS Support
• Enterprise-class plugins
• Commit code and support the Jenkins Community
• Jenkins training and consulting
• Jenkins User Conferences (JUC) and newsletters

4. ©2015CloudBees,Inc.AllRightsReserved
Outline
• Continuous Integration (CI)
o CI with Jenkins
• Continuous Delivery (CD)
o CD with Jenkins
• Jenkins: the Workflow Plugin
• Jenkins: traceability with Puppet/Chef
o The Notification Plugin
• Open Challenges
• Summary
4

5. ©2015CloudBees,Inc.AllRightsReserved
Continous Integration
• The Time To Market critically affects the success of a
product
• The traditional Waterfall model was too slow and did not
easily apply to the reality
• The Agile revolution encouraged:
o Rapid response to changes
o Collaboration across teams
5

6. ©2015CloudBees,Inc.AllRightsReserved
Continuous Integration
• The Concept of Continuous Integration was a first step
that significantly sped up the product lifecycle
o Frequent commits
o Frequent integrations
o Easy detection of problems right after a bad commit
o No necessity to back-track
o Reduction of the integration time
o Increase of productivity
6
Source Code
Quality Analysis
Unit Tests
Binaries

7. ©2015CloudBees,Inc.AllRightsReserved
Jenkins & CI
• Born as hobby project of K.Kawaguchi
• Born with two main objectives:
o Automation of the build
o Automation of the test process
• Completely written in java:
o https://github.com/jenkinsci/jenkins
o https://jenkins.ci.cloudbees.com/
• Most used CI tool
o Plugin architecture
o OSS nature
o Elasticity and Flexibility
7

8. ©2015CloudBees,Inc.AllRightsReserved
Jenkins installations
8

9. ©2015CloudBees,Inc.AllRightsReserved
From Continuous Integration to Continuous
Delivery
• If Continuous Integration (CI) started as automation of the
development-phase only, pretty soon the revolution
embraced:
o The test-phase (QA team)
o The deployment-phase (Ops team)
• Continuous Delivery (CD) was the natural extension of CI,
advocating:
o Collaboration across all the teams involved in the
product life-cycle
o Extensive automation of the delivery process
9

10. ©2015CloudBees,Inc.AllRightsReserved
Jenkins & CD
• Implementing CD means:
o Being able to chain different steps of a cross-
team pipeline
o Automate their execution
• Jenkins is the Hub of CD
10

11. ©2015CloudBees,Inc.AllRightsReserved
DEV
DEV
OPS
QA
Continuous Delivery
11
Source Code
Quality Analysis
Unit Tests
Binaries
PerfsEnvironment
FuncTest Environment
UATEnvironment
Production Environment
GOLIVE!
Release!
Staging Environment

12. ©2015CloudBees,Inc.AllRightsReserved
Implementing CD with Jenkins
• Jenkins aligned to the new concept thanks to plugins able
to:
o Chain jobs together
o Promote the execution of jobs
o Allow human manual intervention
o Monitor the execution through WUI
o Monitor the result of the execution
12

13. ©2015CloudBees,Inc.AllRightsReserved
Implementing CD with Jenkins
• Plugins:
– Build Flow Plugin
– Build Pipeline Plugin
– Build Delivery Pipeline
– …
13

14. ©2015CloudBees,Inc.AllRightsReserved
Implementing CD with Jenkins: the Problem
• Choose the right plugins
• Combine several plugins to obtain different functionalities
• Many atomic jobs chained together
14

15. ©2015CloudBees,Inc.AllRightsReserved
Implementing CD with Jenkins: Workflow
• A single plugin to implement:
– Complex pipelines involving multiple stages
– Not-sequential logic such as loops, forks ..
– Long running builds must survive outages
– Interaction with humans including pauses, input
– Restartable builds in case of transient errors
– Reusable definition to avoid duplication
– Comprehensible scripts with one clear definition
15

16. ©2015CloudBees,Inc.AllRightsReserved
16
Workflow Groovy Script
Parallel steps
Restartability:checkpoints
Manual intervention

17. ©2015CloudBees,Inc.AllRightsReserved
17
Workflow Stage View

18. ©2015CloudBees,Inc.AllRightsReserved
Jenkins and Chef/Puppet Traceability
• Jenkins integrates with Puppet/Chef:
o The Puppet Master/Chef Server will ensure that the
managed server are configured properly before
deploying the artifacts
• When deploying, the traceability is lost:
o Where does the artifact come from?
o Which was the build that generated the artifact?
• Traceability is where the integration between Jenkins and
Puppet/Chef brings value:
o Notification Plugin
18

19. ©2015CloudBees,Inc.AllRightsReserved
19
Traceability in Action

20. ©2015CloudBees,Inc.AllRightsReserved
Open Challenges
• How to do versioning of artifacts that must be continuously
shippable?
o CD nullifies the concept of intermediate versions
• How to trace the environment in which the artifact was
created?
o Today there is no way to capture the environment
used to generate the artifact
20

21. ©2015CloudBees,Inc.AllRightsReserved
Summary
• Jenkins was extended to impersonate the role of
orchestrator in the product lifecycle
• The need of managing the whole CD pipeline required the
implementation of new features:
o Workflow Plugin
o Notification Plugin
• Further steps need to be taken in order to make Jenkins
able to fully embrace the CD revolution:
o Lack of best practices for versioning continuously
shippable artifacts
o Lack of best practices for tracing the build
environment
21

22. ©2015CloudBees,Inc.AllRightsReserved
Questions?
22