the continuous delivery value - codemotion milano 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. !@ingdavidino - Dnsee

MILAN november 28th/29th 2014

The Continuous Delivery Value

MILAN november 28th/29th 2014 – David Funaro

The Continuous Delivery

Value


David Funaro

@ingdavidino

davidfunaro.com


First Release


Release Day


WRONG WAY

This talk is for you…


Overview


Facts

release new features as soon as possible

IT Business

keep system up and running


… with CD

ITBu

sine

ss


RELEASE

FEEDBACK

new features monetize bug

performance layout


RELEASE

? Miss Release Price ?

€


Reaction MetricsC

hang

e

REL

EASE


Reaction MetricsC

hang

e

REL

EASE

Time

Security

Skills

Cost

Predictable

Stress

Repeatability


• How many time you need to release software

Time


• 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


• Have, the selected person, all the skill needed to terminate the procedure ?

• What about his behavior in some exception flow case

Skills


• How many people you need ?

• For how many time ?

• Other Resources ?

Cost


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

Predictable


• What about the stress

• stress => error-prone

Stress


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

Repeatability


Reaction Metrics

REL

EASE

Production


Reaction Metrics

REL

EASE

Production

Time

Security

Skills

Cost

Predictable

Stress

Repeatability


Reaction Metrics

REL

EASE

Production

Staging

Time

Security

Skills

Cost

Predictable

Stress

Repeatability


Reaction Metrics

REL

EASE

Production

Testing

Staging

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

Notify TeamBasic Scenario

Real Time Alerting

Automated Testing

RELEASE


RELEASE


Deploy Pipeline

Commit StageCompile UnitTest Analysis

ReleaseAutomated acceptance

testign

Automated capacity testing

Manual TestingShowcasesExplorarory

testing

example


ContinuousDelivery

Tools

MethodologiesPractices

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


Keep Everything in version control

Automate Almost Everything

If it hurts, do it more frequently

Done means released

Build quality in

Principles


SECTION ISource 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

57

10

Repository


Check-out

Local

Pull

8

29


Check-out

Local

Pull

8

2

9


Check-in

Push

Local

3


Check-in

Push

Local

34


SCM : What it does ?

• Keeping multiple file version

• Collaboration

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

CHECK POINT


Application Evolution


Collaboration


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.


Best Practice

• Little Commit

• Frequent Commit

• Consistent commit

• Use Meaningful Commit message


Different Products


SECTION IIContinuous Integration


Ops

INTEGRATION PROBLEM

(after one commit )

After your commit nothing works anymore

But ... “was working on my computer”


Ops (after deploy in prod)

INTEGRATION PROBLEM

It was working on the stage environment !!!


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

•

sleepless nights before demo ... bug just after release


Resolve defectsC

ost

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 inconsistenciesas 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

FF

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 IIIAutomated 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 ?

RELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASERELEASEfeedback


• Low Risk

• Cheap

• Frequent

• Rapid

• Predictable

Deployment


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 DesktopVersioning update


Problems• Incomplete

• Manual procedure

• Slow

• Server Downtime

• No data migration

• No Rollback


Automated Deployment Goals


one click deploy

Deploy



AnyTime AnyWhere AnyOne



Rollback



no downtime



Scalable

Frontend 1 Frontend 1I Frontend III

Balancer



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 ...

to get the feature 103 done, i 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 ?

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 903OK


A way to setup your environment


Write Configuration

Script


Write Configuration

Script

Versionable


Environment Management


Production TestingStaging


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 IVRealtime Alerting


Waiting for customers feedback ?


Real Time Monitoring

• Application health

• System heatlh

• Services health


Some tools

Mail

Sentry

Log - Exception

Errors Server Monitoring

Application Monitoring


Example - NE


Example - Sentry



Build quality in

Done means released

If it hurts, do it more frequently

Automate Almost Everything


David Funaro

@ingdavidinodavidfunaro.com

Thanks

the continuous delivery value - codemotion milano 2014

Technology