Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
•
2 likes•957 views
Scan-Agile 2011 presentation about how Nextdoor.fi is continuously deployed (within 24 hours) to production
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (20)
Similar to Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
Similar to Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011 (20)
More from Marko Taipale
More from Marko Taipale (20)
Recently uploaded
Recently uploaded (20)
Continuous Deployment – Nextdoor.fi released every day at Scan-Agile 2011
- 1. Continuous Deployment Nextdoor.fi deployed every day Marko Taipale 3.3.2011
- 3. 1. Intro 2. My Context 3. Why & How 4. Lessons learned
- 5. Features written for an application are immediately deployed into production
- 7. Deployment Release
- 10. 30 000 visitors / month 8 days lead time 24/7 monitoring 5 integrations 4 years of Continuous Deployment
- 11. 550+ acceptance tests >80% test coverage 2 bugs (in 4 years)
- 12. 0 people in operations 0 testers 0 full-time developers Production bug fix < 1h
- 13. 3. Why & How
- 16. ”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”
- 18. How do we do it?
- 19. Process and Environments New Test Deploy commit 24h Mainline CI CD Dev Dev Production Test Test Reports Dev TCs Performance test
- 20. Inside ”Test” New Test Deploy commit Unit/Acceptance tests Build CI Report DB update artifacts deployment Performance test Artifacts Reports
- 23. Inside Deploy New Test Deploy commit Version DB SW Backup Reports check migration update DB Biz Failure Backup reports report
- 24. Monitoring Biz reports Business Hearbeat.rb & navigator Application Hearbeat.rb & Monit Containers & DB Monit & Nagios OS & Services Monit & Nagios Hardware
- 27. Continuous Integration Automated tests and Monitoring (Biz & Tech) ”Discipline is the bridge between goals and accomplishment” - Jim Rohn
- 28. 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
- 29. 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
- 30. Marko Taipale @markotaipale huitale.blogspot.com marko.taipale@huitale.com 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