The Continuous Delivery Value - Codemotion Milano 2014

MILAN november 28th/29th 2014
The Continuous Delivery Value
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.
!
@ingdavidino - Dnsee

MILAN november 28th/29th 2014 – David Funaro
The
Continuous Delivery
Value

David Funaro
davidfunaro.com
@ingdavidino

First Release

Release Day

WRONG WAY
This talk is for you…

Overview

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

… with CD
IT
Business

RELEASE
FEEDBACK
new features monetize bug
performance layout

? Miss Release Price ?
RELEASE
€

Reaction Metrics
Change
RELEASE

Reaction Metrics
Change
RELEASE
Time
Security
Skills
Cost
Predictable
Stress
Repeatability

Time
• How many time you need to release
software

Security
• 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) ?

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

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

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

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

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

Reaction Metrics
RELEASE
Production

Reaction Metrics
RELEASE
Production
Time
Security
Skills
Cost
Predictable
Stress
Repeatability

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

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

No Automation Process ?

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

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

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

CD FLOW
Commit /
push
Automated
Deploy
Procedure
Basic Scenario Notify Team
Real Time
Alerting
Automated
Testing
RELEASE

RELEASE

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

Tools
Continuous
Delivery
Practices Methodologies
Cautions

CD Anti-patterns
• Deploy software manually
• Manual Configuration
• First Deploy when development is
complete
• … to a production-like Environment

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

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

SECTION I
Source Code Management

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

SCM : What is it ?
3
5
7
10
Repository

Check-out
Local
Pull
8
29

Check-out
2
9
Local
Pull
8

Check-in
Push
Local
3

Check-in
Push
Local
34

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

MILAN november 28th/29th 2014
CHECK POINT
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.
!
@ingdavidino - Dnsee

Application Evolution

Collaboration

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

Best Practice
• Little Commit
• Frequent Commit
• Consistent commit
• Use Meaningful Commit message

Different Products

SECTION II
Continuous Integration

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

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

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

Resolve defects
Cost
Analysis Design Implementation Testing Release

t
integration
Regression
Working
Broken

t
integration
Regression
Working
Broken
Effort

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

Continuous Integration

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

Requirements
Source Code Management

Requirements

Agile-Testing-Quadrants

CI Flow

F
CI Flow

F
Checkout last Commit
CI Flow
Build and Tests Process

F
F
F
CI Flow

F
F
F
F
F
F
CI Flow

F
F
F
F
F
F
F F
CI Flow

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

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

CI - Output
System Status Documentation/
Artifacts
Quality Check

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

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

Immediate feedback of the health of the system

Ci - software
... more and more

SECTION III Automated Deploy

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

Deploy
A Critical part of the application life-cycle

RELEASE
Real ?

RELEASE
Real ?
RRRRREEEELELLLELEEEAEAAAASSSSESEEEE RRRRREEEELELLLELEEEAEAAAASSSSESEEEE RELEASE
feedback

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

Low Risk
• Exception catched
• Rollback
• Data on secure

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

Frequent
• to get feedback

Rapid

Predictable

Incomplete ways

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

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

Automated
Deployment Goals

Automated Deployment Goals
Deploy
one click deploy

AnyTime AnyWhere AnyOne

Rollback

no downtime

Frontend 1 Frontend 1I Frontend III
Balancer
Scalable

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

Executable code (SCM)

Dependency Management

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

PIP

Data Migration

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

Infrastructure
Management

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

A way to setup your environment

Write
Configuration
Script

Write
Configuration
Script
Versionable

Environment
Management

Staging Production Testing

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

Build a custom Script
• Do a backup
• Create new directory
• Update the code
• Update dependencies
• Run migration data
• Update Environements

Existing Tools
Fabric
... and more others

SECTION IV Realtime Alerting

Waiting for customers
feedback ?

Real Time Monitoring
• Application health
• System heatlh
• Services health

Some tools
Mail
Errors Server Monitoring
Sentry
Log - Exception
Application Monitoring

Example - NE

Example - Sentry

Automate Almost Everything
If it hurts, do it more frequently
Done means released
Build quality in

Thanks
David Funaro
davidfunaro.com
@ingdavidino

The Continuous Delivery Value - Codemotion Milano 2014

Recommended

Recommended

More Related Content

Similar to The Continuous Delivery Value - Codemotion Milano 2014

Similar to The Continuous Delivery Value - Codemotion Milano 2014 (13)

More from David Funaro

More from David Funaro (8)

Recently uploaded

Recently uploaded (20)

The Continuous Delivery Value - Codemotion Milano 2014