Download to read offline
Uploaded bygarrett honeycutt
Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-03-11
Garrett Honeycutt's presentation at Cascadia IT Conference discusses continuous deployment (CD) pipelines, emphasizing the importance of automation and testing in software development. It covers key concepts such as artifact management, monitoring, and the necessity for agility in response to business needs. The talk encourages a culture of testing and failure acceptance to improve deployment reliability and speed.
More Related Content
Similar to Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-03-11
Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-03-11
- 1. Garrett Honeycutt gh@learnpuppet.com learnpuppet.com @learnpuppet Continuous Deployment Pipelinefor Systems 2017-03-11 Cascadia IT Conf Seattle, WA
- 2. # whoami 7th yearat CasitConf! LearnPuppet.com Automation consulting specializing in Puppet
- 3. What is CD? ContinuousDelivery Continuous Deployment
- 4. "Continuous Delivery doesn't meanevery change is deployed to production ASAP. It means every change is proven to be deployable at any time" @ccaum
- 5.
- 6. Fail fast Quick feedbackleads to fixing the issue faster
- 7.
- 8. Boring Deployments Take theexcitement out of making changes
- 9. Putting out fires Reactiveor Proactive?
- 10. MTTR vs MTBF MeanTime to Repair Mean Time Between Failures
- 11.
- 12.
- 13. Debugging Solve one problemat a time
- 14.
- 15. Pipeline Series of stepsthat are tied together through automation
- 16.
- 17.
- 18. Artifact All things necessaryto configure a system.
- 19.
- 20. Artifact You need anartifact store
- 22. Artifact Moves through thepipeline
- 23. Roles Each system hasexactly one
- 24. Profiles Describe technical makeup forroles Site specific data
- 25. Control repo mod 'ssh', :git=> 'https://github.com/ghoneycutt/ puppet-module-ssh.git', :ref => 'v3.49.1'
- 26. Pipeline Let's build areal pipeline.
- 27. Start small Use manualtriggers if needed
- 28. Pipeline Cost and Timerises each step
- 29.
- 30.
- 31. Save artifact Upload toartifact store
- 32. Test config mgmt Rolebased perspective
- 33. Functional testing per role Builda system and verify its state
- 36. Functional testing per role Builda system and verify its state
- 38. Functional testing multi-node Test theentire stack
- 39. Function testing of systems Frompoint of view of consumer
- 40. Tools galore Lot's ofchoices here
- 41.
- 42. Performance Testing Does yournew feature provide worse service?
- 43. Security Testing Find vulnerabilitiesbefore deployment
- 44. Compliance Reporting that showsyou are in compliance
- 45. What to deploy? Codeand data to maintain state
- 46. What to deploy? Entiresystems
- 47. Triggers How does thepipeline start?
- 48.
- 49.
- 50.
- 51.
- 52.
- 53.
- 55.
- 56.
- 57. Control repo # upsteamrepo mod 'ssh', :git => 'https://github.com/ghoneycutt/ puppet-module-ssh.git', :ref => 'v3.49.1' # private module mod 'myapp', :git => 'https://github.com/me/puppet- module-myapp.git', :ref => 'master'
- 58. Triggers How does thepipeline start?
- 59. Where to puttesting scripts? Keep tests close to code
- 60. Information Radiator Let peopleknow what's happening
- 62. ChatOps Tell people whensomething breaks or is deployed
- 63.
- 64. Failing in production Youare not done until you write a test
- 65. Rely on thePipeline Never touching Prod
- 66. Start small 1. Adda different type of testing 2. Write tests 3. Repeat
- 67.
- 68. Garrett Honeycutt gh@learnpuppet.com learnpuppet.com @learnpuppet Continuous Deployment Pipelinefor Systems 2017-03-11 Cascadia IT Conf Seattle, WA