Tweet
Tweet

Slide 1

Slide 1 text

Continuous Delivery @RentTheRunway @markwunsch

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

How RTR achieved Continuous Delivery in the face of legacy code, the ongoing effort to improve our Deployment Pipeline, and how we define good enough.

Slide 4

Slide 4 text

Continuous Delivery You’re doing continuous delivery when: • Your software is deployable throughout its lifecycle • Your team prioritizes keeping the software deployable over working on new features • Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them • You can perform push-button deployments of any version of the software to any environment on demand http://martinfowler.com/bliki/ContinuousDelivery.html Martin Fowler

Slide 5

Slide 5 text

Technical Debt

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

Swimlane

Slide 9

Slide 9 text

Swimlane “…a group of services within a boundary such that any failure within that boundary is contained within the boundary and the failure does not propagate or affect services outside of said boundary.” http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-"swimlaning"/ Fault Isolative Architectures or “Swimlaning”

Slide 10

Slide 10 text

Fault Detection & Fault Isolation http://akfpartners.com/techblog/2008/05/30/fault-isolative-architectures-or-"swimlaning"/ Fault Isolative Architectures or “Swimlaning”

Slide 11

Slide 11 text

PDP User Static Grid Home Checkout

Slide 12

Slide 12 text

PDP User Static Grid Home Checkout Heroku Engine Yard Rackspace views assets base api_clients

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

run Rack::URLMap.new({ "/home" => RTR::HomeApp, "/pages" => RTR::PagesApp, "/grid" => RTR::GridApp, "/designers" => RTR::DesignersApp, "/pdp" => RTR::PDPApp, "/user" => RTR::UserApp, "/account" => RTR::AccountApp, "/self_service" => RTR::SelfServiceApp, "/shortlist" => RTR::ShortlistApp, "/appointments" => RTR::ShowroomApp, "/ourrunway" => RTR::MomentsApp, "/order" => RTR::CheckoutApp, "/queue" => RTR::QueueApp, "/" => RTR::HomeApp })

Slide 19

Slide 19 text

Storefront base api_clients *

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

• You can perform push-button deployments of any version of the software to any environment on demand

Slide 22

Slide 22 text

http://www.thinkgeek.com/product/15a5/

Slide 23

Slide 23 text

• Your software is deployable throughout its lifecycle

Slide 24

Slide 24 text

GitHub Flow https://guides.github.com/introduction/flow/index.html

Slide 25

Slide 25 text

http://martinfowler.com/bliki/FeatureToggle.html Flaggregator™

Slide 26

Slide 26 text

• Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them

Slide 27

Slide 27 text

Fashionator: fashionator at your service! Fashionator: DEPLOY: rtr_ruby_storefront[v2014.07.21.1622] was deployed to sf01.prod.renttherunway.it,sf02.prod.renttherunway.it,sf03.prod.renttherunway.it Mark: good robot Fashionator: *:゜☆ヽ(*’∀’*)/☆゜:。*。 Fashionator™ https://hubot.github.com/

Slide 28

Slide 28 text

• Your team prioritizes keeping the software deployable over working on new features

Slide 29

Slide 29 text

Good Enough

Slide 30

Slide 30 text

• Daily Deploy • Release Quarterback • diminishing returns • YAGNI

Slide 31

Slide 31 text

Kaizen 改善

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

Everyone deserves a Cinderella Experience

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content