1. Continuous Delivery
Dream => Reality
Dr. Clement Escoffier, akquinet

2. This is a work of fiction. Names,
characters, places and projects are all
products of the author‟s imagination.
Any resemblance to actual events,
locales or projects is entirely
coincidental

3. SITUATION
Again, purely imaginary ;-)

4. Quite a big project
• Running for 2 years
• 4-6 developers
• Agile (Scrum)

5. As in all big projects,
the build is chaotic

6. Taking forever,
Intermittent failures,
Inconsistent output,
Non-reproducible builds,
Authorization failures
…

7. Releasing => Stress
=> Delays
Delivery => Error-prone

8. Delays => Customer 

9. Trust  => Pressure 

10. Quality  => Technic. Debt 
=> Non optimal project situation

11. “Let‟s deliver
a version every day”
Output from an escalation meeting

12. Did you say “deliver” ?
• Web App, JavaEE…
• Up and Running
• Mobile App
• Downloadable or in a Market
• Desktop App
• Installers, Market, Auto-update
• Installed on a system

13. Developers
More Releases => 

14. Project Managers
More Paperwork => 

15. Ops
More Changes => 

16. CONTINUOUS DELIVERY –
THE CHALLENGE
Seamless Disruptive Changes

17. How to introduce
continuous delivery
seamlessly ?

18. “Let‟s all commit to a
continuous delivery model
…

19. … but without
changing the way
we work”

20. CONTINUOUS DELIVERY –
PRINCIPLES
Will try to make it not so boring

21. Delivery anti-patterns
• Manual software building and
deployment
• Deploying in production-like
environment only after releasing
• Manual configuration of the
environment

22. A set of good practices to
simplify software delivery
Automation
Responsibility
Pipeline

23. Automation

24. Bootstrap / Configuration
[Insert your own] Tests
Release, Deployment Process
Database Evolution

26. Commit Capacity
Stage UI Tests Tests
Acceptance Deployment Release
Tests Tests

27. It‟s not only source code…

28. Source
Environment Data
Configuration

29. Build tools
&
Build processes

30. Source Code Data
Deployment Script
Evolutions
Check-in everything
Configuration
Environment Build Scripts
Description

31. Unique Versioning Tags
Human-readable
Traceability
Introspectable
Notifications Reproducible
Build

32. Commit Often Use „branch
by abstraction‟
Avoid branches
Continuous Integration
Understandable
Test Suites
Fast feedback
Comprehensive
Tests

33. Unit Tests Integration
Tests
Test Groups
Automate Tests
Deployment
Tests
UI Tests System
Tests

34. Describe your Avoid
environment Dev vs. Prod
Always deploy
the same way
Automate Deployment
Manage
configurations
Do it Did I tell you to
frequently TEST ?
Plan
rollbacks

35. Implement a test
strategy

36. Commit Stage V2 V3
V1
Test + Package
Acceptance Tests
UI Tests
Deployment Tests
Capacity Tests
Promotion / Release
<<Prod Ready>>

37. Source Repository
Commit Acceptance Prom. / Rel.
Stage Tests Stage
V3 V3
Artifact Repository

38. The Commit Stage
• As fast as possible
• < 5 min is good
• < 10 min is acceptable
mvn clean install
• Package, Changelog, Scripts…

39. Build only one package:
Distribution

40. This package is reused
by all the test phases

41. Describe your
environment

42. Reduce the distance between
Dev & Prod

43. Always deploy using
the same way

44. BACK TO OUR PROJECT
Implementation Time

45. SCM => SVN, Git, Git-SVN

46. Build Tool => Maven

47. continuous-versioning-mp+
maven-release-plugin

48. CI => Jenkins

49. Artifact Repo => Nexus

50. Development
• Maven build A
• -SNAPSHOT 1.0.0-SNAPSHOT
• Continuous B
1.0.0-SNAPSHOT
Versioning
C
1.0.0

51. Virtual Environment
• Vagrant
• http://vagrantup.com/

52. Virtual Environment
• Provisioned using
• Shell script
• Puppet Manifests
• Chef Recipes
=> Your deployment script

53. Commit Stage
Source Repository
mvn clean install
1.0.0-SNAPSHOT
Artifact Repository

54. Commit Stage
Source Repository
tag
mvn clean install Fast-Release
1.0.0-SNAPSHOT 1.0.0_42
Artifact Repository

55. All other stages are using
the _42 version

56. Testing Stages
Initialize a new VM
+
Deployment
Integration Deployment UI
Tests Tests Tests
Vagrant Box

57. Testing Stages
Deployment on a
staging system
Deployment UI Deployment Other
Tests Tests Tests again Tests
Vagrant Box Staging System

58. Releasing

59. Releasing Promoting

60. Take the current staged version (RC)
=> Declare it as G.A.

61. TOOLING

62. Build Tools
• Builds
• Reproducible
• Avoid system deps
• Make, Ant, Maven, Gradle, SB
T

63. Virtualization
• Avoid „works on my machine‟
• Dev/ Test / Run on prod-like
system
• Vagrant is awesome

64. Continuous Integration
• Customizable
• Pipeline concepts
• Jenkins, Hudson, Team City,
Bamboo
• Travis

65. CMS
• Describe your environment
• Treat your infra as code
• Shell Script, Puppet, Chef

66. Application Deployer
• Specific CMS to deploy your
application
• Go, Deploy-it,
Puppet/Mcollective, JMX

67. SOME FINAL WORDS

68. Responsibility

69. Following the rules

70. Trust is back

71. Seeing changes

72. Always being ready

73. Track & Visualize everything

74. Danke !