Continuous Delivery in Ruby

Continuous Deliveryin RubySrushti Ambekallu Brian Guthrie@srshti @bguthriegithub.com/srushti github.com/bguthrie

Delivering great software

Continuous Integration

1.Unit and integration tests

RSpec or Test::Unit

Tests of speciﬁc units of code Tests of multiple layersTests of external integration points

Receive new commitReset testdatabase schema Run tests Reset test data

1.Unit and integration tests2.Automated acceptance tests

Cucumber or the test runner of your choice

Selenium or Sahi Capybara

Receive new commitReset test Run Resetdatabase browser test data schema tests Restart test server

1.Unit and integration tests2.Automated acceptance tests3.User acceptance tests

type click click click click

type click click click click click click click click click type

type click click click click click click click click click type clickclick click type

type click click click click click click click click click click type click clickclick click type

click type click type click click click click click click click click click click click click type click clickclick click type

click type click type click click click click click click ERROR click click click click click click type click clickclick click type

1.Unit and integration tests2.Automated acceptance tests3.User acceptance tests

1.Unit and integration tests2.Automated acceptance tests2a.Deploy3.User acceptance tests

Deployment

Super easy in Ruby(those Java guys are suckers)

$ ssh root@production.com

$ ssh root@production.comprod:~ root# cd /var/www/site

$ ssh root@production.comprod:~ root# cd /var/www/siteprod:~ root# git pull a31a0eb569ba2

$ ssh root@production.comprod:~ root# cd /var/www/siteprod:~ root# git pull a31a0eb569ba2prod:~ root# bundle install

$ ssh root@production.comprod:~ root# cd /var/www/siteprod:~ root# git pull a31a0eb569ba2prod:~ root# bundle installprod:~ root# rake db:migrate

$ ssh root@production.comprod:~ root# cd /var/www/siteprod:~ root# git pull a31a0eb569ba2prod:~ root# bundle installprod:~ root# rake db:migrateprod:~ root# rake jammit:package

$ ssh root@production.comprod:~ root# cd /var/www/siteprod:~ root# git pull a31a0eb569ba2prod:~ root# bundle installprod:~ root# rake db:migrateprod:~ root# rake jammit:packageprod:~ root# touch tmp/restart.txt

$ cap deploy production

Why automate?

Digression: The Rails deploy model

$ ssh root@production.com

$ ssh root@production.comprod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2

$ ssh root@production.comprod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2

$ ssh root@production.comprod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2prod:~ root# bundle install

$ ssh root@production.comprod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2prod:~ root# bundle installprod:~ root# rake db:migrate

$ ssh root@production.comprod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2prod:~ root# bundle installprod:~ root# rake db:migrateprod:~ root# rake jammit:package

$ ssh root@production.comprod:~ root# git clone git@scm/myapp.git /var/www/site/a31a0eb569ba2prod:~ root# ln -s /var/ww/site/current /var/www/site/a31a0eb569ba2prod:~ root# bundle installprod:~ root# rake db:migrateprod:~ root# rake jammit:packageprod:~ root# touch tmp/restart.txt

ci-server:~/app/ $ bundle install --deploymentci-server:~/app/ $ rake jammit:packageci-server:~/app/ $ tar zxvf app-<SHA>.tgz *

RVMNot for production

$ cat ~/projecta/.rvmrcrvm jruby@projecta$ cat ~/projecta/.rvmrcrvm ree@projectb$ cat ~/projecta/.rvmrcrvm 1.9.1@projectc

Environments

Appserver

Appserver Appserver Appserver

Appserver Background jobs server Appserver Appserver

App server Background jobs server App Load serverbalancer App server

App server Background jobs server App Load serverbalancer App server Background jobs server App server

ChefPuppet

App server Background jobs server App Load serverbalancer App server Background jobs server App server

ConﬁgurationManagement App server Background jobs server App Load server balancer App server Background jobs server App server

Peace in the kingdom

How often?

Project Lifecycle faf4d2788f ......................... a433f20abbCode Release Six months

Project Lifecycle faf4d2788f f26115c8c c86c1bfea6 56d1dd8accc4 dd35192f8 1b51fee653a f038af17de4 8318b750aec 192410bd2537 631f5c3f58c 7bcafdd2266 2bbed3e4bd2Code Release Every week (iteration)

Project Lifecycle f26115c8c dd35192f8 f038af17de4 631f5c3f58c 7bcafdd2266Code Release Every day?

Project Lifecycle 7bcafdd2266Code Release Multiple times a day??

Features long in development need branches

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 %>

This doesn’t work for everything: big features, conﬁg changes

Branch by source control (“fork me”) http://martinfowler.com/bliki/FeatureBranch.html

The Build Pipeline

“...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

Unit and Automated ManualIntegration Acceptance Acceptance Production (Woohoo!) Tests Tests Tests

Test Test Test runner runner runner Test runner Unit and Automated ManualIntegration Acceptance Acceptance Production (Woohoo!) Tests Tests Tests

“I see CI as primarily giving birth to a releasecandidate at each commit. The job of the CIsystem and deployment process is to disprovethe production-readiness of a release candidate.This model relies on the need to have somemainline that represents the current shared, mostup to date picture of complete.” - David Farley

Automate until human intervention = decision DEPLOY

Internal External users users Feature User Continuousdevelopment Staging acceptance Production integration Bug ﬁxes testing

Human beings

Real testing is hardLet computers do the simple testing Smart humans for smart testing

Automated testing User testingTraditional projects

Automated testing User testingAgilify!

Agilify!

Questions? Srushti Ambekallu @srshti github.com/srushti Brian Guthrie @bguthrie github.com/bguthrie

http://blog.c42.in	1426
http://blog.brianguthrie.com	297
http://www.thoughtworks.com	25
http://lanyrd.com	24
http://blog.bangaloreruby.org	23
url_unknown	12
http://feeds.feedburner.com	9
http://localhost:4000	8
http://posterous.com	7
http://cache.baidu.com	4
http://blogs.thoughtworks.com	4
http://translate.googleusercontent.com	2
http://webcache.googleusercontent.com	2
http://twitter.com	2
http://static.slidesharecdn.com	1

Continuous Delivery in Ruby

by Brian Guthrie on May 31, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

15 Embeds 1,846

Statistics

Continuous Delivery in Ruby — Presentation Transcript