System Crash, failure data migration, partial update: issues that no one would ever want to meet during the deploy and ... hoping for the best is not enough. The deployment activity is important as those that precede it. The Continuous Delivery will give you low risk, cheap, fast, predictable delivery and ... soundly.

1. The Continuous DeliveryValue
12 - 04 - 2014
ROME 11-12 April 2014
David Funaro
Crash dei sistemi, Migrazioni fallite, aggiornamenti interrotti: sono tutte problematiche che
nessuno vorrebbe mai incontrare durante l'introduzione di nuove funzionalità nel proprio
applicativo (deploy) e ... la speranza non basta. L'attività di deploy è importante tanto quanto
quelle che la precedono. La Continuous Delivery è un insieme di strumenti e metodologie che
permetteranno di rendere i rilasci a basso rischio, economici, veloci, predicibili e ... sonni tranquilli.
d.funaro@dnsee.com

2. The
Continuous Delivery
Value
12 - 04 - 2014

3. David Funaro
@ingdavidino
davidfunaro.com

4. First Release

5. Release Day

6. WRONG WAY
This talk is for you…

7. Overview

8. Facts
keep system up and running
release new features as
soon as possible
IT Business

9. … with CD
IT
Business

10. RELEASE
FEEDBACK
new features monetize bug
performance layout

11. RELEASE
? Miss Release Price ?
€

12. Reaction MetricsChange
RELEASE
Time
Security
Skills
Cost
Predictable
Stress
Repeatability

13. • How many time you need to release
software
Time

14. • Everything will be ok ?
• Can i be sure that every needed step will
be done ?
• Exceptions, are managed ?
• Data migration goes well ?
• Can i go back (rollback) ?
Security

15. • Have, the selected person, all the skill
needed to terminate the procedure ?
• What about his behavior in some
exception flow case
Skills

16. • How many people you need ?
• For how many time ?
• Other Resources ?
Cost

17. • are you able to indicate how much time will
care ?
Predictable

18. • What about the stress
• stress => error-prone
Stress

19. • Just finish a deploy. Software released.A bug
is found.You have to re-start the deploy
procedure
Repeatability

20. Reaction Metrics
RELEASE Production
Testing
Staging
Time
Security
Skills
Cost
Predictable
Stress
Repeatability

21. No Automation
Process ?

22. Lots of things to
consider
• Code evolution
• Code dependency management
• System evolution management
• Data management and architecture
• Component management

23. Software Release
• Low Risk
• Cheap
• Frequent
• Rapid
• Predictable
... should be
Continuous Delivery

24. CD requirements
• Source Code Management
• Continuous Integration Server
• Automated Deploy
• Real Time Alerting
• Root Cause Analysis

25. CD FLOW
Commit /push
Automated
Testing
FAIL
SUCCESS Automated
Deploy
Procedure
notify
Basic Scenario

27. Deploy Pipeline
Commit Stage
Compile
UnitTest
Analysis
Build Installers
Release
Automated
acceptance
testign
Automated
capacity
testing
Manual Testing
Showcases
Explorarory
testing
example

28. Continuous
Delivery
Tools
MethodologiesPractices
Cautions

29. Anti-patterns
• Deploy software manually
• Manual Configuration
• Deploy to a production-like Env Only after
development is complete

30. Benefits
• Empower Team
• Reducing Errors
• Lowering Stress
• Deployment Flexibility
• Practice Make Perfect

31. Keep Everything in version control
Automate Almost Everything
Principles
If it hurts, do i more frequently
Done means released
Build quality in

32. SECTION I
Source Code Management

33. i sent you a mail with
the last change
... are you
shure ?
i can’t find the new file ?!?
The problem

35. SCM :What is it ?
3
5
7
10
Repository

36. Local
Check-out
Pull
8
29

37. Check-in
Push
Local
3 4

38. SCM :What it does ?
• Keeping multiple file version
• Collaboration

39. CHECK POINT

40. Application Evolution

41. Collaboration

42. isn’t just for source code
Cautions
you need everything required to re-create your
application’s binaries and the environments in
which they run.

43. Best Practice
• Little Commit
• Frequent Commit
• Consistent commit
• User Meaningful Commit message

44. Different Products

45. SECTION II
Continuous Integration

46. After your commit
nothing works anymore
Ops
INTEGRATION PROBLEM
(after one commit )
After your commit nothing
works anymore
But ...“was working on my
computer”

47. Ops(after deploy in prod)
INTEGRATION PROBLEM
It was working on the stage
environment !!!

48. sleepless nights before demo ... bug just after release

49. Cost
Analysis Design Implementation Testing Release
Resolve defects

50. t
integration
Regression
Working
Broken
Effort

51. In software development the components
integration need to be tested continuosly...
!
in order to find inconsistencies
as soon as possible
Good Solution

52. Continuous Integration

53. Continuous Integration is a software
development practice where members of a team
integrate their work frequently, usually each
person integrates at least daily - leading to
multiple integrations per day.
Each integration is verified by an automated
build (including test) to detect integration errors
as quickly as possible.
Martin Fowler

54. Requirements
Source Code Management

55. Requirements

56. Agile-Testing-Quadrants

57. F
F
F
F
F
FF
F
Checkout last Commit
CI Flow
Build andTests Process

58. Build & Test
✓Process creating executable code
✓Unit test
✓Quality criteria
✓FunctionalTest
✓Non FunctionalTest
Valid Syntax Compile
Code behavior
Code coverage, Mass detector
Business Acceptance Criteria
Application performance
PASS

59. CI - Reduce Risk
• Say goodbye to long and tense integrations
• Increase visibility which enables greater communication
• Catch issues fast and nip them in the bud
• Spend less time debugging and more time adding features
• Proceed in the confidence you’re building on a solid foundation
• Stop waiting to find out if your code’s going to work
• Reduce integration problems allowing you to deliver software
more rapidly

60. CI - Output
System Status Documentation/Artifacts Quality Check

61. “Continuous Integration doesn’t get rid of bugs, but it
does make them dramatically easier to find and
remove.”
Martin Fowler

62. Ci - Best practice
• CI server === Production Server
• Integrate it from the first commit
• Find best way to get notified

63. Immediate feedback on the health of the system

65. Ci - software
... more and more

66. SECTION III
Automated Deploy

67. Deployment
“is all the activities that make a software
system available for use”
Wikipedia

68. A Critical part of the application
life-cycle
Deployment

69. RELEASE
Real ?
RELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASE
feedback

70. Deployment
• Low Risk
• Cheap
• Frequent
• Rapid
• Predictable

71. Low Risk
• Exception catched
• Rollback
• Data on secure

72. Cheap
• no more than one click
• no more than one person
• no skilled person

73. Frequent
• to get feedback

74. Rapid

75. Predictable

76. Incomplete ways

77. is that a deploy procedure ?
$ git pull origin master
$ svn update
Remote Desktop Versioning update

78. • Incomplete
• Manual procedure
• Slow
• Server Downtime
• No data migration
• No Rollback
Problems

79. Automated Deployment Goals

80. one click deploy
Deploy
Automated Deployment Goals

81. AnyTime AnyWhere AnyOne
Automated Deployment Goals

82. Rollback
Automated Deployment Goals

83. no downtime
Automated Deployment Goals

84. Scalable
Frontend 1 Frontend 1I Frontend III
Balancer
Automated Deployment Goals

85. Deployment Elements
• Executable Code
• Dependency Management
• Software configuration
• Infrastructure Management
• Data Migrations
• Manage Cache
• Manage Assets

86. Executable code (SCM)

87. Dependency Management

88. How you keep updated your libraries
dependencies ?
to get the feature 103 done, i
use library XXX
ok, i’ll note it
here ...
to get the feature 103 done, i
use library XXX
OK

89. PIP

91. Data Migration

92. What if, after your first production
deployment, you have to change the Entity
Relationship ?

94. Infrastructure Management

95. How you keep updated your OS componets/
libraries ?
to get the feature 103 done, i
use library XXX, that require
the module 288
ok, i’ll note it
here ...
to get the feature 103 done, i
use library XXX, that require
the module 903
OK

96. A way to setup your environment

97. Write
Configuration
Script
Versionable

98. Environment Management

99. Production TestingStaging

100. Manual - Follow recipe
• Integrity problems
• Problem with exception handling
• Basic Skills requirements
• Time consuming - expensive
• Error - prone
• Stress

101. Build a custom Script
• Do a backup
• Create new directory
• Update the code
• Update dependencies
• Run migration data
• Update Environements
• Warm up cache
• ...

103. Existing Tools
Fabric
... and more others

104. Build quality in
Done means released
If it hurts, do i more frequently
Automate Almost Everything
Keep Everything in version control

106. David Funaro
@ingdavidino
davidfunaro.com
Thanks