Your SlideShare is downloading. ×
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

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

1,765

Published on

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

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

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,765
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
23
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Continuous Deployment Nextdoor.fi deployed every day Marko Taipale 3.3.2011
  • 2. 1. Intro2. My Context3. Why & How4. Lessons learned
  • 3. Features written for an application areimmediately deployed into production
  • 4. Transaction cost
  • 5. Deployment Release
  • 6. 2. www.nextdoor.fi
  • 7. What?Who?Why?
  • 8. 30 000 visitors / month8 days lead time24/7 monitoring5 integrations4 years of Continuous Deployment
  • 9. 550+ acceptance tests>80% test coverage2 bugs (in 4 years)
  • 10. 0 people in operations0 testers0 full-time developersProduction bug fix < 1h
  • 11. 3. Why & How
  • 12. ”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”
  • 13. How do we do it?
  • 14. Process and Environments New Test Deploy commit 24h Mainline CI CDDevDev Production Test Test Reports Dev TCs Performance test
  • 15. Inside ”Test” New Test Deploy commit Unit/Acceptance tests Build CI Report DB updateartifacts deployment Performance test Artifacts Reports
  • 16. Inside Deploy New Test Deploy commit Version DB SWBackup Reports check migration update DB Biz FailureBackup reports report
  • 17. MonitoringBiz reports BusinessHearbeat.rb& navigator ApplicationHearbeat.rb& Monit Containers & DBMonit &Nagios OS & ServicesMonit &Nagios Hardware
  • 18. 4. Lessons learned
  • 19. Continuous Integration Automated tests and Monitoring (Biz & Tech)”Discipline is the bridge between goalsand accomplishment”- Jim Rohn
  • 20. 5 steps to get it started1.Continuous Integration + Automated acceptance tests + Definition of Ready2.Stop-the-line3.Simple Deployment Script4.Real Time Alerting5.Root cause analysis
  • 21. Where to go from here http://bit.ly/OxJv http://slidesha.re/d5L9H9 http://slidesha.re/sHpYV http://bit.ly/eEDL30 http://bit.ly/cZLR9M
  • 22. Marko Taipale @markotaipale huitale.blogspot.com marko.taipale@huitale.comI help companies to improve byshowing what I have donehow I have done it andwhat I have learned about it.I am a CTO of a lean startup

×