Continuous Delivery - Mr. Vu Hong Phat

www.axon.vnfb.com/AxonActiveVietNam
• Problem
• Continuous Delivery introduction
• Tools
• Demo
• Benefits
• Principles
• CD vs. CI vs. Continuous Deployment
• Gotchas
Agenda
Continuous Delivery

Delivery
1/41Continuous Delivery

Scenario
Continuous Delivery 2/41

How often they deliver
(source : https://www.thoughtworks.com/insights/blog/case-continuous-delivery)
11.6 seconds, May - 2011
twice a day
multiple times a week
multiple times a day

How?

www.axon.vnfb.com/AxonActiveVietNamContinuous Delivery 5/41

Continuous delivery actually written in the
first principle
Our highest priority is to satisfy
the customer through early
and continuous delivery
of valuable software.
Agile manifesto’s principles

Definition
Continuous Delivery is a set of principles and practices to reduce
the cost, time, and risk of delivering incremental changes to
users
Martin Fowler

Definition
Continuous Delivery is a software development discipline where
you build software in such a way that the software can be
released to production at any time
Martin Fowler

Definition

www.axon.vnfb.com/AxonActiveVietNamContinuous Delivery
(https://goo.gl/zhUWsC)
11/41

• Problem
• Continuous Delivery introduction
• Tools
• Demo
• Benefits
• Principles
• CD vs. CI vs. Continuous Deployment
• Gotchas
Agenda

Tools

Advance

A ‘Super’ calculator
RESTful GET request example:
PROD:
http://203.113.164.230/core_service/calculator/add?num
1=2&num2=3
Continuous Delivery
RESTful services
15/41

Calculator pipeline
Continuous Delivery
.develop
.check out
.int-test
(dev)
.develop
.check out
.build war
.unit test
.firebug
.deploy
(dev)
.master
.check out
.build war
.unit test
.firebug
.deploy
(pre-prod)
.master
.check out
.int-test
(pre-prod) .war (from
pre-prod)
.deploy
(prod)
Auto Manual
16/41

Repositories
17/41

I dome some changes in RESTful service

Pipeline

Source code (in app)

Source code (RESTful service)

Story 1
As a developer, I want to add a new
“divide” function into the app.
So that, user can use the app to
calculate divide operation.
• Endpoint: /calculator/divide?
num1=<num1>&num2=<num2>
• E.g. : num1 = 4.2, num2 = 2
the result is : 2.1

Story 2
As a developer, I want to add new
parameter to the “divide” endpoint
So that, it formats returned value in
decimal places.
• Update endpoint:
/calculator/divide?num1=<num1>&num2=<num
2>&scale=<scale>
• Example:
/calculator/divide?num1=1&num2=3&scale=3
result:
{
"result": 0.333,
"success": "true”
}

Reduced deployment risk
• Deploy smaller changes
• Fix issue soon
Benefits

Reliable progress
• "done" means "developers declare it to be done“
• “done” means “released” to production.
Benefits

User feedback
• End up building something that isn't useful ?
• Get feedback quickly once deliver frequently.
• Employees -> Premium customers -> all customers
Benefits

• The process for releasing/deploying software MUST be
repeatable and reliable
• Automate almost everything
Principles

• If something difficult or painful, do it more often
• improve it, probably automate it
• make it painless and easy
• Keep everything in source control
who doesn’t keep everything in source control?
Principles

• Done means “released”
• “I’ve checked in my code so it’s done at my computer”.
• More reliable, if changes are deployed into a production
(or production-like) environment.
Principles

• Build quality in
• Good, targeted quality metrics (unit tets, integration tests,
performance tests, etc)
• Improve continuously
• Don’t let your system to become out of date or impossible
to maintain
Principles

• 200k test suites in the code base
• Run 10M test suites per day
• 60M individual test cases / day and growing.
• 4000 continuous integration builds
(source : http://www.wired.com/2015/09/google-2-billion-lines-codeand-one-place/)

• Everybody has responsibility for the release process
• Make money
• Get products released to customers
• Keep in mind
• Developers: how to deploy them?
• Testers: should test for deployment defects
• PMs: plan projects with attention to deployment
Principles

• Continuous Integration (CI) 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 check-in is then verified by an automated build, allowing
teams to detect problems early.
Continuous Integration vs. Continuous Delivery

• CI usually refers to integrating, building, and testing code
within the development environment. CD builds on this,
dealing with the final stages required for production
deployment.
• In order to do CD you must be doing CI

Continuous Delivery vs. Continuous Deployment

Where we started?
• Process / practices
• Done means ?
• Modeling the development and delivery pipeline
• Must apply CI
• Git, branches
• Automated tests
• Tools
• Continuous Deployment is optional
• Improve time by time

Gotchas
Continuous Delivery
• Branches
• master
• develop
• userstory_1
• bug_001
39/41

Gotchas
• Each environment need different configurations. I don’t
want to change the source code to deploy on production.
• Configuration saved on DB on each environment.
• When deploying, get these configuration then ‘inject’ to our source code.
• Log level
• Development, testing : DEBUG
• Integration : INFO
• Production : INFO or ERROR

Pipeline
Conclusion
Fast
Frequently
Reliable
Jenkins
Continuous Delivery
Automated testing
Continuous Deployment
Continuous Integration
Mindset
Principles
Benefits

Step 1: Scan the QR code or
access the link
http://zingpoll.com/SMS
Step 2: Choose the option and
submit
Thanks for you feedbacks

Continuous Delivery - Mr. Vu Hong Phat

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Continuous Delivery - Mr. Vu Hong Phat

Similar to Continuous Delivery - Mr. Vu Hong Phat (20)

More from Scrum Breakfast Vietnam

More from Scrum Breakfast Vietnam (20)

Recently uploaded

Recently uploaded (20)

Continuous Delivery - Mr. Vu Hong Phat