30
Continuous Deployment Marko Taipale 3.3.2011 Nextdoor.fi deployed every day

Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

  • View
    1.971

  • Download
    1

Embed Size (px)

DESCRIPTION

Scan-Agile 2011 presentation about how Nextdoor.fi is continuously deployed (within 24 hours) to production

Citation preview

Page 1: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Continuous Deployment

Marko Taipale

3.3.2011

Nextdoor.fi deployed

every day

Page 2: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 3: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

2. My Context

1. Intro

3. Why & How

4. Lessons learned

Page 4: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 5: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Features written for an application are

immediately deployed into production

Page 6: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Transaction cost

Page 7: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Deployment

Release

Page 8: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

2. www.nextdoor.fi

Page 9: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Why?

Who?

What?

Page 10: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

30 000 visitors / month

8 days lead time

24/7 monitoring

5 integrations

4 years of Continuous Deployment

Page 11: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

550+ acceptance tests

>80% test coverage

2 bugs (in 4 years)

Page 12: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

0 people in operations

0 testers

0 full-time developers

Production bug fix < 1h

Page 13: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

3. Why & How

Page 14: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 15: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 16: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

”We need to wait for end of the sprint!”

– Bazooka Team

”KISS – we do not need to configure that”

”Most time in bug fixing is spent on finding it”

Page 17: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 18: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

How do we do it?

Page 19: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Process and Environments

New commit

Test Deploy

CIProduction

Test Reports

Performance

test

DevDev

TestDev

Mainline24h

CD

TCs

Page 20: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Build artifacts

DB updateCI

deployment

Unit/Acceptance tests

Performance test

Report

Artifacts Reports

New commit

Test Deploy

Inside ”Test”

Page 21: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 22: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 23: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

New commit

Test Deploy

Inside Deploy

Backup ReportsVersion check

DB migration

SW update

DB

Backup

Biz

reports

Failure

report

Page 24: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Monitoring

Business

Application

Containers & DB

OS & Services

Hardware

Biz reports

Hearbeat.rb

& navigator

Hearbeat.rb

& Monit

Monit &

Nagios

Monit &

Nagios

Page 25: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Page 26: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

4. Lessons learned

Page 27: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Continuous Integration

Automated tests and Monitoring (Biz & Tech)

”Discipline is the bridge between goals

and accomplishment”- Jim Rohn

Page 28: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

5 steps to get it started

1.Continuous Integration + Automated

acceptance tests + Definition of Ready

2.Stop-the-line

3.Simple Deployment Script

4.Real Time Alerting

5.Root cause analysis

Page 29: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

Where to go from here

http://bit.ly/OxJv

http://slidesha.re/d5L9H9

http://bit.ly/eEDL30

http://slidesha.re/sHpYV

http://bit.ly/cZLR9M

Page 30: Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011

I help companies to improve by

showing what I have done

how I have done it and

what I have learned about it.

I am a CTO of a lean startup

Marko Taipale

@markotaipale

huitale.blogspot.com

[email protected]