Alm Forum 2014 - Jose Luis Soria - Patterns and anti-patterns for (Continuous) delivery
Download as PPTX, PDF4 likes2,017 views
The document discusses various anti-patterns related to software delivery and continuous delivery practices. It identifies issues such as failing to version control components, manually performing deployment tasks, complex deployment procedures, lack of automation, not validating in production-like environments, lack of rollback preparation, rebuilding software multiple times, and an overall lack of a well-defined delivery process. It recommends corresponding patterns to address these anti-patterns, such as versioning everything, automating all tasks, one-click deployments, deploying to production-like environments, preparing for rollbacks, building only once, and establishing a robust release pipeline.
Alm Forum 2014 - Jose Luis Soria - Patterns and anti-patterns for (Continuous) delivery
- 1. Sponsored by
- 2. Patterns & anti-patterns for (Continuous) Delivery Jose Luis Soria jlsoria@plainconcepts.com @jlsoriat
- 4. backupbackup
- 5. get an old versionget an old version
- 13. wasted time
- 15. accidents
- 17. Doyoumanually copy orchangeconfig files to matchtarget environments?
- 18. figure out what to change
- 24. not testing on certain environments
- 27. 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
- 29. So,youdon’t haveanyinformation abouthow the systemwill behavein prod?
- 30. Deploy to a copy of production
- 31. 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
- 34. Is the business losinglots ofmoney meanwhile?
- 38. errors introduced by the buildsequence
- 39. wasted time and resources
- 40. Build only once
- 42. sensitive steps left for the last moment
- 43. critical aspects of delivery not beingmastered
- 45. Bring the pain forward
- 47. failing to deliver effectively
- 48. Build a Release Pipeline
- 50. 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
- 51. 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