Continuous Delivery in Ruby
9 likes2,415 views
The document discusses continuous delivery in Ruby, focusing on the importance of automated testing and deployment processes. It outlines various types of tests including unit, integration, automated acceptance, and user acceptance tests, as well as the deployment steps involved. Additionally, it emphasizes the benefits of automation in software delivery and managing project lifecycles effectively.
Continuous Delivery in Ruby
- 1. Continuous Delivery in Ruby Srushti Ambekallu Brian Guthrie @srshti @bguthrie github.com/srushti github.com/bguthrie
- 7. 1.Unit and integration tests
- 9. Tests of specific units of code Tests of multiple layers Tests of external integration points
- 10. Receive new commit Reset test database schema Run tests Reset test data
- 11. Receive new commit Reset test database schema Run tests Reset test data
- 12. 1.Unit and integration tests 2.Automated acceptance tests
- 13. Cucumber or the test runner of your choice
- 14. Selenium or Sahi Capybara
- 15. Receive new commit Reset test Run Reset database browser test data schema tests Restart test server
- 16. 1.Unit and integration tests 2.Automated acceptance tests 3.User acceptance tests
- 18. type click click click click
- 19. type click click click click click click click click click type
- 20. type click click click click click click click click click type click click click type
- 21. type click click click click click click click click click click type click click click click type
- 22. click type click type click click click click click click click click click click click click type click click click click type
- 23. click type click type click click click click click click ERROR click click click click click click type click click click click type
- 24. 1.Unit and integration tests 2.Automated acceptance tests 3.User acceptance tests
- 25. 1.Unit and integration tests 2.Automated acceptance tests 2a.Deploy 3.User acceptance tests
- 26. Deployment
- 27. Super easy in Ruby (those Java guys are suckers)
- 29. $ ssh [email protected] prod:~ root# cd /var/www/site
- 30. $ ssh [email protected] prod:~ root# cd /var/www/site prod:~ root# git pull a31a0eb569ba2
- 31. $ ssh [email protected] prod:~ root# cd /var/www/site prod:~ root# git pull a31a0eb569ba2 prod:~ root# bundle install
- 32. $ ssh [email protected] prod:~ root# cd /var/www/site prod:~ root# git pull a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate
- 33. $ ssh [email protected] prod:~ root# cd /var/www/site prod:~ root# git pull a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate prod:~ root# rake jammit:package
- 34. $ ssh [email protected] prod:~ root# cd /var/www/site prod:~ root# git pull a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate prod:~ root# rake jammit:package prod:~ root# touch tmp/restart.txt
- 35. $ cap deploy production
- 36. Why automate?
- 37. Digression: The Rails deploy model
- 39. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2
- 40. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2 prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2
- 41. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2 prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2 prod:~ root# bundle install
- 42. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2 prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate
- 43. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2 prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate prod:~ root# rake jammit:package
- 44. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2 prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate prod:~ root# rake jammit:package prod:~ root# touch tmp/restart.txt
- 45. $ ssh [email protected] prod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2 prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2 prod:~ root# bundle install prod:~ root# rake db:migrate prod:~ root# rake jammit:package prod:~ root# touch tmp/restart.txt
- 46. ci-server:~/app/ $ bundle install --deployment ci-server:~/app/ $ rake jammit:package ci-server:~/app/ $ tar zxvf app-<SHA>.tgz *
- 47. RVM
- 49. $ cat ~/projecta/.rvmrc rvm jruby@projecta $ cat ~/projecta/.rvmrc rvm ree@projectb $ cat ~/projecta/.rvmrc rvm 1.9.1@projectc
- 50. Environments
- 51. App server
- 53. App server Background jobs server App server App server
- 54. App server Background jobs server App Load server balancer App server
- 55. App server Background jobs server App Load server balancer App server Background jobs server App server
- 56. Chef
- 57. Chef Puppet
- 58. App server Background jobs server App Load server balancer App server Background jobs server App server
- 59. Configuration Management App server Background jobs server App Load server balancer App server Background jobs server App server
- 61. Peace in the kingdom
- 62. How often?
- 63. Project Lifecycle faf4d2788f ......................... a433f20abb Code Release Six months
- 64. Project Lifecycle faf4d2788f f26115c8c c86c1bfea6 56d1dd8accc4 dd35192f8 1b51fee653a f038af17de4 8318b750aec 192410bd2537 631f5c3f58c 7bcafdd2266 2bbed3e4bd2 Code Release Every week (iteration)
- 65. Project Lifecycle f26115c8c dd35192f8 f038af17de4 631f5c3f58c 7bcafdd2266 Code Release Every day?
- 66. Project Lifecycle 7bcafdd2266 Code Release Multiple times a day??
- 67. Features long in development need branches
- 68. Branch by abstraction (“if this feature is enabled, show this link”) <% if feature?(:masala) %> <%= render :partial => "dosas/masala", :locals => { :dosa => @dosas.masala.first } %> <% else %> <%= render :partial => "dosas/plain", :locals => { :dosa => @dosas.first } %> <% end %>
- 69. This doesn’t work for everything: big features, config changes
- 70. Branch by source control (“fork me”) http://martinfowler.com/bliki/FeatureBranch.html
- 72. “...an automated manifestation of your process for getting software from version control into the hands of your users.” - Jez Humble and David Farley, Continuous Delivery
- 73. Unit and Automated Manual Integration Acceptance Acceptance Production (Woohoo!) Tests Tests Tests
- 74. Test Test Test runner runner runner Test runner Unit and Automated Manual Integration Acceptance Acceptance Production (Woohoo!) Tests Tests Tests
- 75. “I see CI as primarily giving birth to a release candidate at each commit. The job of the CI system and deployment process is to disprove the production-readiness of a release candidate. This model relies on the need to have some mainline that represents the current shared, most up to date picture of complete.” - David Farley
- 76. Automate until human intervention = decision DEPLOY
- 77. Internal External users users Feature User Continuous development Staging acceptance Production integration Bug fixes testing
- 81. Human beings
- 83. Real testing is hard Let computers do the simple testing Smart humans for smart testing
- 84. Automated testing User testing Traditional projects
- 85. Automated testing User testing Agilify!
- 86. Agilify!
- 87. Questions? Srushti Ambekallu @srshti github.com/srushti Brian Guthrie @bguthrie github.com/bguthrie
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: Brian - skeptic (&#x201C;what do I need tests for?&#x201D;)\nSrushti - champion\n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: Brian - champion (&#x201C;I deploy all the time - I GUESS you could automate&#x201D;)\nSrushti - skeptic\n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: \n
- #51: \n
- #52: \n
- #53: \n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: \n
- #61: \n
- #62: \n
- #63: \n
- #64: \n
- #65: Brian - champion, Srushti - skeptic\n
- #66: \n
- #67: \n
- #68: \n
- #69: \n
- #70: \n
- #71: \n
- #72: \n
- #73: \n
- #74: \n
- #75: \n
- #76: \n
- #77: Brian - more rapid, then convinced to be slower\nSrushti - slower, then convinced to be more rapid\n
- #78: \n
- #79: \n
- #80: \n
- #81: \n
- #82: \n
- #83: \n
- #84: \n
- #85: \n
- #86: \n
- #87: Brian - skeptic because wants slower deploys, Srushti - champion\n
- #88: \n
- #89: \n
- #90: \n
- #91: \n
- #92: \n
- #93: \n
- #94: \n
- #95: \n
- #96: Etsy - will open source later\n
- #97: Brian - skeptic (&#x201C;I used to have an army of testers&#x201D;)\nSrushti - champion\n
- #98: \n
- #99: \n
- #100: \n
- #101: \n
- #102: \n
- #103: \n