Downloaded 42 times
![Cycle Time
“How long would it take your organization to
deploy a change [to production] that involves
just one single line of code? Do you do this on a
repeatable, reliable basis?”
- Mary and Tom Poppendieck,
Implementing Lean Software Development
7](https://image.slidesharecdn.com/continuousdeliveryapplied-agiledc-121024140046-phpapp02/75/Continuous-Delivery-Applied-AgileDC-7-2048.jpg)
Uploaded byMike McGarr
Continuous Delivery Applied (AgileDC)
The document discusses continuous delivery, emphasizing practices aimed at building, testing, and releasing software more efficiently. It highlights the importance of deployment pipelines and automation in achieving faster and more reliable software releases, while also addressing challenges like configuration management and stress during manual deployments. Additionally, it provides resources for further reading and tools to facilitate continuous delivery processes.
More Related Content
Similar to Continuous Delivery Applied (AgileDC)
Continuous Delivery Applied (AgileDC)
- 1. Continuous Delivery Applied Mike McGarr jmcgarr@gmail.com @jmichaelmcgarr http://earlyandoften.wordpress.com http://www.meetup.com/DC-continuous-integration/
- 2. About Me • J.Michael (Mike) McGarr • 11 years as a consultant, Excella Consulting • Founder of the DC Continuous Integration, Delivery, and Deployment Meetup 2
- 3. Continuous Delivery is… …aset of practices and principles aimed at, building, testing, and releasing software faster and more frequently. 3
- 4.
- 5. “Our highest priorityis to satisfy the customer through early and continuous delivery of valuable software.” - First of the Twelve Principles behind the Agile Manifesto 5
- 6. Quality or Speed 6
- 7. Cycle Time “How longwould it take your organization to deploy a change [to production] that involves just one single line of code? Do you do this on a repeatable, reliable basis?” - Mary and Tom Poppendieck, Implementing Lean Software Development 7
- 8. The Last Mile Manual Deployments Insufficient Configuration Management Infrequent, Error Prone Deployments 8
- 9.
- 10. Frequent Automated Deployments http://flic.kr/p/29Ree 10
- 11.
- 12. Continuous Deployment Deployment Pipelines Deployment Automation Configuration Continuous Management Testing Integration Agile 12
- 13.
- 14. Deployment Pipelines A DeploymentPipeline is an automated manifestation of your process for getting software from version control into the hands of your users. 14
- 15. Deployment Pipelines (aka Build Pipelines) 15
- 16. Continuous what? Continuous Continuous Continuous Integration Delivery Deployment 16
- 17. Where do Istart?
- 18. Understand your Process http://www.michaelnygard.com/blog/2008/02/outrunning_your_headlights.html 18
- 19.
- 20. Developers http://flic.kr/p/5cK2 20
- 21.
- 22.
- 23.
- 24. Static Code Analysis CheckStyle 24
- 25.
- 26. The Team 26
- 27. Agile 27
- 28.
- 29. Continuous Integration Check-in Daily Commit to Trunk Automate the Build Keep the Build Fast Every Commit results in Build Test in Clone of Production Automate Deployment 29
- 30. Testing 30
- 31.
- 32. Testing is nota Phase http://flic.kr/p/6bcg 32
- 33.
- 34.
- 35.
- 36.
- 37.
- 38. Build Once, DeployMany 38
- 39. Externalize Configuration ESCAPE Database 39
- 40.
- 41. Traceability 41
- 42.
- 43.
- 44. Deploying 44
- 45. Deployment Pipelines (aka Build Pipelines) 45
- 46. Build Pipeline inJenkins 46
- 47.
- 48.
- 49.
- 50.
- 51. Puppet 51
- 52. Vagrant 52
- 53. Monitoring (sucks) https://github.com/monitoringsucks 53
- 54.
- 55.
- 56. Further Reading • ContinuousDelivery: Reliable Software Releases through Build, Test and Deployment Automation, by Jez Humble and David Farley - http://www.amazon.com/Continuous-Delivery-Deployment-Automation- Addison-Wesley/dp/0321601912 • Test Driven Development (TDD) – http://en.wikipedia.org/wiki/Test- driven_development • Introducing BDD, by Dan North – http://dannorth.net/introducing-bdd/ • Agile Manifesto – http://agilemanifesto.org/ • Scrum – http://www.scrumalliance.org/learn_about_scrum • Continuous Integration, by Martin Fowler – http://martinfowler.com/articles/continuousIntegration.html • Specification by Example, by Gojko Adzic - http://specificationbyexample.com/ • Build Pipelines - http://www.magpiebrain.com/2009/12/13/a-brief-and- incomplete-history-of-build-pipelines/ 56
- 57. Further Reading • MavenReleases on Steriods, by Axel Fontaine – http://www.axelfontaine.com/2011/01/maven-releases-on-steroids- adios.html • What is in a Name? Usually a version number, actually., by James Betteley - http://jamesbetteley.wordpress.com/2011/07/07/what-is-in-a- name-usually-a-version-number-actually/ • Build Once, Deploy Many - http://earlyandoften.wordpress.com/2010/09/09/build-once-deploy- many/ • Evolutionary Design - http://martinfowler.com/articles/designDead.html • Continuous Deployment - http://timothyfitz.wordpress.com/2009/02/08/continuous-deployment/ • Sonar’s Technical Debt Calculation - http://www.sonarsource.org/evaluate-your-technical-debt-with-sonar/ • Gherkin - https://github.com/cucumber/cucumber/wiki/Gherkin • Branch by Abstraction, by Paul Hammat - http://paulhammant.com/blog/branch_by_abstraction.html 57
- 58. Tools • Git - http://git-scm.com/ • Subversion - http://subversion.tigris.org/ • Mercurial - http://mercurial.selenic.com/ • Rational ClearCase - http://www- 01.ibm.com/software/awdtools/clearcase/ • Serena Dimensions CM - http://www.serena.com/products/dimensions- cm/index.html • Ant - http://ant.apache.org/ • Ivy - http://ant.apache.org/ivy/ • Maven - http://maven.apache.org/ • Gradle - http://gradle.org/ • JUnit – http://www.junit.org/ • Findbugs – http://findbugs.sourceforge.net/ • PMD – http://pmd.sourceforge.net/ • Checkstyle – http://checkstyle.sourceforge.net/ 58
- 59. Tools • Jenkins -http://jenkins-ci.org/ • Jenkins Performance Plugin – https://wiki.jenkins- ci.org/display/JENKINS/Performance+Plugin • Jenkins Build Pipeline Plugin - https://wiki.jenkins- ci.org/display/JENKINS/Build+Pipeline+Plugin • Nexus – http://www.sonatype.org/nexus/ • Artifactory – http://www.jfrog.com/products.php • Sonar – http://www.sonarsource.org/ • Cucumber – http://cukes.info/ • Liquibase – www.liquibase.org/ • Flyway – http://code.google.com/p/flyway/ • Escape – http://code.google.com/p/escservesconfig/ • Capistrano - https://github.com/capistrano/capistrano • Puppet – http://puppetlabs.com/ • Chef – http://www.opscode.com/chef/ • Vagrant – http://vagrantup.com/ • JMeter – http://jmeter.apache.org/ 59
- 60. Tools • Nagios - http://www.nagios.org/ • Logstash – http://logstash.net/ • StatsD – https://github.com/etsy/statsd • Ganglia – http://ganglia.sourceforge.net/ • Metrics – https://github.com/codahale/metrics • Graphite - http://graphite.wikidot.com/ 60
Editor's Notes
- #8 Cycle Time is a measure of Continuous Delivery maturity
- #9 Collaboration (DEV + Customer, DEV + Operations)Talking early and often…break down walls. [DevOps]Automation. Automate Everything! Build, Test, Deploy!Frequency. Frequent means small. Easier to troubleshoot, rollback. Reduces Risk.Feedback. Change triggers feedback. Feedback is fast. Team acts on it.
- #10 Manual DeploymentsInsufficient Configuration ManagementInfrequent, Error Prone Deployments