Alm Forum 2014 - Jose Luis Soria - Patterns and anti-patterns for (Continuous) delivery
Upcoming SlideShare
Loading in...5
×
 

Alm Forum 2014 - Jose Luis Soria - Patterns and anti-patterns for (Continuous) delivery

on

  • 361 views

Slides for my presentation about delivery patterns at the ALM Forum 2014 (Seattle)

Slides for my presentation about delivery patterns at the ALM Forum 2014 (Seattle)

Statistics

Views

Total Views
361
Views on SlideShare
361
Embed Views
0

Actions

Likes
3
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Alm Forum 2014 - Jose Luis Soria - Patterns and anti-patterns for (Continuous) delivery Alm Forum 2014 - Jose Luis Soria - Patterns and anti-patterns for (Continuous) delivery Presentation Transcript

  • Sponsored by
  • Patterns & anti-patterns for (Continuous) Delivery Jose Luis Soria jlsoria@plainconcepts.com @jlsoriat
  • Doyoufailto versiondatabases, configfiles,dependencies, documentation,tools or environments?
  • backupbackup
  • get an old versionget an old version
  • undo changesundo changes
  • collaboratecollaborate
  • track changestrack changes
  • baselinebaseline
  • Version everything
  • Doyoumanually build,package, deploy,test, or provisionenvironments?
  • mistakes (missing steps,misunderstandings, boredom,etc.)
  • wasted time
  • dependency on specific people
  • accidents
  • Automate everything
  • Doyoumanually copy orchangeconfig files to matchtarget environments?
  • figure out what to change
  • omissions, mistakes
  • sensitive info being exposed
  • Tokenize configuration
  • Doyoufollowa complex, multi-stepprocedurefor deployments?
  • wasted time and effort
  • not testing on certain environments
  • Setup one-click deployments
  • http://bit.ly/1mKGTqB
  • ARIANNE 5 EXPLOSION (1996) The Ariane 5 rocket was reusing software from the Ariane 4. Ariane 5’s faster engines exploited an undiscovered bug: the software tried to cram a 64- bit number into a 16-bit space. 36.7 seconds into its launch, the self destruct safety mechanism was activated. http://en.wikipedia.org/wiki/Ariane_5#Notable_launches
  • Doyouvalidateonly indev/test environments?
  • So,youdon’t haveanyinformation abouthow the systemwill behavein prod?
  • Deploy to a copy of production
  • AT&T NETWORK CRASH (1990) The failure of one switching system would cause a message to be sent to nearby switching units, making those other systems to fail too – resulting in a cascading failure across the entire AT&T long distance network http://en.wikipedia.org/wiki/List_of_software_bugs#Telecommunications
  • Areyouprepared to recoverfromfailure?
  • Doesittakea lotoftime andeffort?
  • Is the business losinglots ofmoney meanwhile?
  • Preparefor rollbacks
  • Doyourebuildfromthesame code severaltimes duringreleases?
  • shipping non-tested binaries
  • errors introduced by the buildsequence
  • wasted time and resources
  • Build only once
  • Doyouconsistentlyavoidpainfulsteps inyourdeliveryprocess?
  • sensitive steps left for the last moment
  • critical aspects of delivery not beingmastered
  • http://bit.ly/70eM6U
  • Bring the pain forward
  • Doyoulacka defined,repeatable,robust andfast deliveryprocess?
  • failing to deliver effectively
  • Build a Release Pipeline
  • What aboutyour ownpatterns &practices? 1. Thinkabout some delivery practice not covered in the talk. 2. Tweet it. #almforum @jlsoriat 3. Get acopy of the book! http://aka.ms/ReleasePipeline
  • Thanks! Get my e-book(forfree): http://aka.ms/ReleasePipeline Buyit: http://amzn.to/1fuo1YO Get thelabs: http://aka.ms/ReleasePipeline-HOL #almforum@jlsoriat jlsoria@plainconcepts.com