The document discusses the implementation of continuous delivery (CD) in enterprise environments, highlighting the benefits such as reduced application costs and accelerated market time. It outlines the challenges faced in achieving CD, such as standardizing job parameters and automating deployment processes, while providing a five-step framework for organizations to adopt CD effectively. Additionally, it emphasizes the importance of automated testing and integrating deployment into the continuous integration cycle.

1. Introducing
Con-nuous
Delivery
in
the
Enterprise
Andrew
Phillips,
XebiaLabs

2. Andrew Phillips
o VP Product Mangement for XebiaLabs
o Lots of enterprise software development on
high-performance systems
o Been on both sides of the “Dev…Ops” fence
o Active open source contributor and committer:
jclouds, Multiverse, Gradle and others
o Cloud, PaaS & JVM language fan (esp. Scala, Clojure)
o Regular meetup, conference etc. presenter
A Bit About Me…

3. Our flagship product, Deployit, is a market-leading
Application Release Automation platform.
o Headquartered in Boston, Massachusetts
o Global development and support offices in
US, NL, UK, France and India
About XebiaLabs
Benefits include:
o Reduce development applications costs
o Accelerate application time to market
o Bridge the gap between Development and Operations

4. o 1min on Continuous Integration
o Continuous Delivery in a Nutshell
o Enterprise Challenges to CD
o A Continuous Delivery Automation Platform
o 5 Steps Towards Continuous Delivery
o Convincing Your Management
Agenda

5. o Emerged at the end of the 90s as one
of the XP practices
o By continuously building and testing
software quality should improve
o Tests often limited to unit tests (e.g.
JUnit)
o Sometimes also functional tests (e.g.
Selenium)
The 1min Continuous Integration Intro

6. o Emerged at the end of the 90s as one
of the XP practices
o By continuously building and testing
software quality should improve
o Tests often limited to unit tests (e.g.
JUnit)
o Sometimes also functional tests (e.g.
Selenium)
The 1min Continuous Integration Intro

7. Beyond CI
o Deployment to the target platform
often not part of the CI cycle
o Deployment procedures not tested!
o Application not tested on ultimate
target platform!

8. Beyond CI
o Principle #1 of the Agile Manifesto:
“Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software.”
o What is the business value of code sitting
in your repository?

9. Enter Continuous Delivery

10. Enter Continuous Delivery

11. Enter Continuous Delivery
o Full-scale implementation: Every
(tagged) version goes to production
o Ramping up: Include deployment in
the CI cycle to test the deployed
artifacts on the target platform

12. Enter Continuous Delivery
o Smoke tests
o Landing page
o Line of Life
o Functional tests on target platform (e.g. Selenium)
o Content of the landing page
o Typical run
o Performance tests (e.g. JMeter)
o Response time of the landing page
o Response time of the simple / complex path

13. Enter Continuous Delivery

14. Enterprise Challenges
o Organizing many jobs
o Standardizing common job parameters
o Identifying job ownership
o Securing job access
o Automating job sequence
o Setting up job gates/conditions

15. Enterprise Challenges
o Same pipeline setup across middleware and OS
types
o Same pipeline setup in private/hybrid cloud and
PaaS environments
o On-demand environment provisioning
o Release Management integration
o End-to-end “paper trail”

16. A Continuous Delivery Automation Platform
Cloud/Virtualization Providers
Environment Provisioning
Continuous
Integration
Deployit
Deployment Automation
Build Test Automation
Runtime Control
IT Ops Analytics
Release Coordination
Quality &
Monitoring
Feature Delivery

17. A Continuous Delivery Automation Platform
EC2, vSphere etc.
Puppet Enterprise
Jenkins Enterprise
DEV@cloud
Deployit

18. Sample Delivery Pipeline

19. Sample Delivery Pipeline

20. Sample Delivery Pipeline: Recap
o Enterprise features:
o Folders
o Templates
o Access-control
o Job gates
o Validated merge
o “Smart” deployment automation
o “Smart” environment provisioning
o Key ingredient: automated tests!

21. 5 Steps Towards Continuous Delivery
1. Define extent and branches of pipeline
o Doesn’t have to be Prod straight away!

22. 5 Steps Towards Continuous Delivery
1. Define extent and branches of pipeline
o Doesn’t have to be Prod straight away!
2. Define triggers and gates for your pipeline phases
o How many of these can you automate?

23. 5 Steps Towards Continuous Delivery
1. Define extent and branches of pipeline
o Doesn’t have to be Prod straight away!
2. Define triggers and gates for your pipeline phases
o How many of these can you automate?
3. Do only validated code/artifacts get passed
down the pipeline?
o Watch out if new components are introduced
later on

24. 5 Steps Towards Continuous Delivery
4. Who needs to know/be able to control what?
o Job settings and deployed configuration
settings can be invisible

25. 5 Steps Towards Continuous Delivery
4. Who needs to know/be able to control what?
o Job settings and deployed configuration
settings can be invisible
5. How much variation across projects/platforms do
you need to handle?

26. o They already do it…
Convincing Your Management
and many more…

27. Convincing Your Management
o Your competitors are working on it…

28. o Application Release Trends 2013 Survey
o go.xebialabs.com/Survey2013.htm
o Dzone Refcard: “Preparing for Continous Delivery”
o refcardz.dzone.com/refcardz/preparing-continuous-
delivery
o “Introducing Continuous Delivery in the Enterprise”
o go.xebialabs.com/
EBCDWhitepaper_Continuous_Delivery.html
o Continuous Delivery Automation
o www.xebialabs.com/continuous-delivery
More Information

29. Thank You!
NEXT STEPS
o More information: www.xebialabs.com
GET STARTED
o Deployit Trial: www.xebialabs.com/trial
Deployit: www.xebialabs.com/products
Blog: blog.xebialabs.com
Twitter: @xebialabs
YouTube: youtube.com/xebialabs
STAY INFORMED