This document discusses continuous delivery and DevOps practices using Jenkins and Puppet. It defines DevOps as addressing security at every stage and having high-performing teams that spend less time fixing issues. It also discusses the DevOps trinity of people, processes, and tools. Jenkins Pipelines and infrastructure as code with Puppet are presented as key practices for continuous delivery. The integration of Jenkins and Puppet Enterprise is demonstrated for automating application deployments.

1. Continuous delivery &
DevOps with Jenkins and
Puppet
Everything as Code
Brian Dawson & Carl Caum

2. Carl Caum
Technical Marketing Manager
Puppet

3. Brian Dawson
DevOps Evangelist
CloudBees

4. DevOps
It’s about giving a shit

5. Sound familiar?
5
“Why won’t Ops just make this
change? It’s small”
“Don’t the developers know
anything about logging?”
“Why does it take so long for Ops
to deploy this code?”
“Why can’t the developers
build packages?”
“The devs don’t care that this
code doesn’t scale.”
“Ops won’t let us use the latest
Ruby for some reason.”

6. The cause
6
Dev Ops

7. Empathy rarely
extends beyond our
line of sight.

8. The solution
8
Dev OpsDevOps

9. …. except not really though
Product Delivery Process
Problem
Statement
Problem
Prioritization
Design /
Development Deployment Monitoring
Engineering
OpsProduct
management DevOps?DevOps?
DevOps?

10. Shared goals with
transparency and
accountability build
a shared sense of
purpose.

11. DevOps
Why are we even talking about it?

13. High-performing organizations
are decisively outperforming
their lower-performing peers
in terms of throughput.

14. Because they address security
at every stage, high-performing
teams spend less time fixing
security issues.

15. Get your copy of the
2016 State of DevOps Report
puppet.com/devops-report-2016

16. DevOps
Great...err, but what is it?

17. 17
The DevOps Trinity
17
Upstream Downstream
People &
Culture
Process &
Practices
Tools &
Technology
Agile, Scrum, Kanban PMBOK, ITIL, etc
Point Tools,
Grassroots, Rapid Change
Move Fast, Innovate Maintain Quality Stability, Uptime
Enterprise class, Stable,
Repeatable, traceable
Define Plan Code Build Integrate Test Release Deploy Operate

18. Culture
Automation
Measurement
Sharing

19. The Three Ways - Gene Kim

20. Systems Thinking
Understand the performance of the entire system, not each
individual silo
20

21. Amplify Feedback Loops
Build quick, short, feedback into the process
21

22. Culture of Experimentation and Learning
Enforce a culture of continuous experimentation, risk taking, and
learning.
22

23. Continuous Delivery
Prove every change is deployable

24. 24
The DevOps Trinity and the Chasms
24
Upstream Downstream
People &
Culture
Process &
Practices
Tools &
Technology
Agile, Scrum, Kanban PMBOK, ITIL, Waterfall etc
Point Tools,
Grassroots, Rapid Change
Move Fast, Innovate Maintain Quality Stability, Uptime
Enterprise class, Corp
procurement, Stable
Define Plan Code Build Integrate Test Release Deploy Operate

25. 25
The Foundation
25
Upstream Downstream
People &
Culture
Process &
Practices
Tools &
Technology
Agile, Scrum, Kanban PMBOK, ITIL, Waterfall etc
Point Tools,
Grassroots, Rapid Change
Move Fast, Innovate Maintain Quality Stability, Uptime
Enterprise class, Corp
procurement, Stable
Define Plan Code Build Integrate Test Release Deploy Operate

26. https://www.perforce.com/pdf/continuous-delivery-report.pdf
26

27. 27
continuous
deployment
continuous
deliverycontinuous integration
DevOps → Cultural focus on shared objectives
Reliable
Repeatable
Fast
agile
CD and DevOps in Context
27

28. 28
Software changes
continuously
deployed to live
production
continuous
deployment
Software changes
continuously delivered to
stakeholders in any
environment
continuous
deliverycontinuous integration
Automated commit, build and testing of
code in the development environment
Feedback
Rapid Changes
Discipline
agile
An incremental
approach to
identifying,
prioritizing, and
coordinating feature
development
Development Production / Prod-like Live Production
Env.Stage
Release Deploy Monitor
Upstream (left) Downstream (right)
Define Plan Code Commit Build Non-Func Test Scan Integrate Int. Test Package Deploy Acct. Test Load Test
Change Mgt.
Production
CD and DevOps in Context
28
DevOps → Cultural focus on shared objectives

29. Continuous delivery doesn’t mean every change is
deployed to production ASAP
But with every change it is release ready
(which includes depoyable!)

30. 30
Automation is the Key
Photo courtesy of Steve Jurvetson via Flickr

31. Jenkins
Continuous integration and delivery tool

32. 32
Complex Delivery Pipelines
Delivery of App and Config
Robust and Highly Available
Results Report
SOURCE
CODE
CONTROL
SYSTEM
Code
Commit
</>
Development Production
Continuous Integration/Delivery
Commit Build Test Stage Deploy
P
P
P
Jenkins – #1 Automation Platform for CI àCD

33. 3333© 2016 CloudBees, Inc. All Rights Reserved.
Code & Commit Build & Config Scan & Test Release Deploy
Over 1.2 Million Users 1200+ plugins cover every
stage of delivery
Jenkins is the Hub of Continuous Delivery

34. Why?

35. It connects all
the things

36. It’s extensible

37. Source: State of Jenkins Survey Sept. 2015
How Do We Know?

38. Source: 2016 Jenkins Community Survey

39. Mission Possible: Make CD Accessible to All
Cross functional
Accessible
Simplified
Visual
Maintainable

40. Pipeline-as-code
Declarative Pipeline
Blue Ocean
+
Infrastructure-as-code
The future of CD

41. 4141
Drive CD with Jenkins Pipeline
Development Production
Commit Build Stage Deploy
? ?
Pipelines Need:
P Branching
P Looping
P Restarts
P Checkpoints
P Manual Input
Sonar Test
Selenium Test
Perf Test
Jenkins Pipeline

42. Pipeline as Code
Introduce “pipeline” as a first class in Jenkins
Codify stages into an explicit Jenkinsfile in your source repository
Resumability/durability of the pipeline state
Extend the DSL with your own steps
github.com/jenkinsci/pipeline-examples

43. 43
Pipeline DSL
node('docker') {
checkout scm
/* Grab the abbreviated SHA1 of our pipeline’s commit.*/
sh 'git rev-parse HEAD > GIT_COMMIT'
def shortCommit = readFile('GIT_COMMIT').take(6)
stage 'Build'
def image = docker.build("jenkinsciinfra/bind:build-${shortCommit}")
stage 'Deploy'
image.push()
}

44. 44
Jenkins Pipeline Stage View
Restartable Checkpoints
Artifact Downloads

45. 45
Declarative Pipeline
Pipelines can now be defined with a simpler syntax.

46. 46
Blue Ocean - Pipeline Creation

47. 47
Blue Ocean - Pipeline Visualization

48. 48

49. Tools & Technologies enable “crossing the chasm”
Normalized
✓ Language and
practice agnostic
✓ Not Dev or Ops
specific
✓ Distributed
Rich Integration
Support
✓ Tools as
microservices
✓ Modular
Automated
✓ Repeatability
✓ Reportability
✓ Flexibility
Confidence In
Downstream
Deliverables
✓ Support supply-
chain
✓ Traceability
✓ Immutability
✓ Measure and report
Scale To
Enterprise
✓ Cross-domain
visibility metrics
✓ Security and
governance
✓ Supported
49

50. Puppet Enterprise
And Jenkins
Promote & Deploy with Puppet

51. The toolchain
… across all technologies.
Version control
Infrastructure
automation
Continuous Integration
Deployment
automation
Monitoring
and
others
…
and
others
…
and
others
…

52. Where to start
Infrastructure as Code
Collaboration IterationFast Feedback Visibility
Infrastructure
Automation
Version Control
& Peer Review
Continuous
Integration &
Delivery
Automated
Testing
Deployment
Automation

53. Infrastructure as code and
continuous delivery pipelines push
quality to the left, getting ever
closer to the keyboard.

54. Push quality left
● Infrastructure code is portable
● Infrastructure code is repeatable
● Puppet is idempotent (same result
regardless of beginning state)
● Puppet is declarative (less DevOoops)

55. Puppet Enterprise
Orchestration

56. Example application
App relies on multiple services that span infrastructure
Glass Fish F5 LB
App API
Kerberos
SSH
Log stash
WebSphere
App API
SSH
Log stash
F5 LB MS SQL

57. Database
HTTP
Example application
Use Puppet language to model your application
WebSphereApp API
SSHLog stash
F5 LB
MS SQL
● Services
● Relationships
● Dependencies
● Instances
– Dev, Staging, Production, etc.

58. Example application
Puppet Enterprise determines order and deploys your application.

59. Puppet Enterprise
Code Management

60. Code management
● Know exactly when your Puppet code
deployments are complete
● Control who can deploy code into
what areas with built-in integration to
Role-Based Access Control
Deploy code confidently with a new command line interface and API

61. Jenkinsfile
Everything as code

64. Demo

65. So what?
Use cases

66. Infrastructure Pipelinehttps://github.com/puppetlabs/jenkins-pipeline-puppet-enterprise-plugin/blob/master/
examples/Jenkinsfile-infrastructure_pipeline

67. Application Deploymentshttps://github.com/puppetlabs/jenkins-pipeline-puppet-enterprise-plugin/blob/master/
examples/Jenkinsfile-application_service_pipeline

68. Canary Deploymentshttps://github.com/puppetlabs/jenkins-pipeline-puppet-enterprise-plugin/blob/master/
examples/Jenkinsfile-canary_deployments

69. Phased Deploymentshttps://github.com/puppetlabs/jenkins-pipeline-puppet-enterprise-plugin/blob/master/
examples/Jenkinsfile-canary_deployments

70. Jenkins Update Center
Available today

71. Tier 2 CloudBees Certified
In the next few weeks

72. Questions
https://puppet.com/Jenkins
https://go.cloudbees.com