Continuous Delivery
•
119 likes•15,209 views
An introduction to the concepts behind Continuous Delivery as well as an introduction to some of the tools available for implementing continuous delivery practices on a new project. This presentation is geared towards Java developers, but is applicable to all.
Report
Share
More Related Content
What's hot
What's hot (20)
Similar to Continuous Delivery
Similar to Continuous Delivery (20)
More from Mike McGarr
More from Mike McGarr (19)
Recently uploaded
Recently uploaded (20)
Continuous Delivery
- 1. Continuous DeliveryMike McGarrmike.mcgarr@excella.comhttp://earlyandoften.wordpress.com @jmichaelmcgarr
- 2. About MeJ. Michael (Mike) McGarr
- 4. Lead of Excella’s Java Center of Excellence
- 5. Java Developer for over 11 years
- 6. Interests:
- 8. XP & Agile
- 9. Automation
- 10. Testing
- 12. AgendaStoryWhat is Continuous Delivery?Core PracticesTools3
- 13. Typical Project4Analyst & CustomerRequirementsArchitectDesignDeveloperDevelopmentTesterQAOperationsRelease
- 15. 6Problems with WaterfallLong QA feedback loopLack of collaborationInability to change direction
- 16. WaterFall Project7Analyst & CustomerRequirementsArchitectDesignDeveloperDevelopmentTesterQAOperationsMonths!Release
- 18. Agile Project9Customer & TeamCustomer & TeamCustomer & TeamRequirementsRequirementsRequirementsTestTestTestDevelopmentDevelopmentDevelopmentOperationsReleaseDays!TheLast Mile?Months!
- 19. 10The Last MileManual DeploymentsInsufficient Configuration ManagementInfrequent, Error Prone Deployments
- 21. AgendaStoryWhat is Continuous Delivery?Core PracticesTools12
- 23. 14
- 24. 15
- 25. …a set of practices and principles aimed at, building, testing, and releasing software faster and more frequently.16Continuous Delivery is…
- 26. “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”- First of the Twelve Principles behind the Agile Manifesto17
- 28. “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 Development19Cycle Time
- 32. AgendaStoryWhat is Continuous Delivery?Core PracticesTools23
- 33. 24Core Practices
- 34. 25Continuous DeploymentBuild PipelinesDeployment AutomationConfigurationManagementContinuous IntegrationTestingAgile
- 35. 26Configuration ManagementVersion Everything!Single Identifier DependenciesApp ConfigurationsDataEnvironments
- 37. 28Continuous IntegrationCheck-in DailyCommit to Trunk Automate the BuildKeep the Build FastEvery Commit results in BuildTest in Clone of ProductionAutomate Deployment
- 38. 29Recommended PracticesExtreme Programming (XP)Fail a Build for Design BreachesFail a Build for Slow TestsFail a Build for Warnings & Code Style Breaches
- 39. 30Testing
- 40. 31Kinds of TestsUnit TestsIntegration TestsFunctional/Acceptance TestsPerformance & Load TestsPenetration TestsExploratory Tests
- 41. 32Testing StrategyIdentify and Prioritize Project RiskDecide what Actions to TakeTests = Executable SpecificationsConfidence
- 42. 33
- 43. 34Testing RecommendationsAutomate your TestsUse Fakes/MocksAutomated Acceptance Testing
- 44. 35Automated Acceptance TestsFast FeedbackReduce Tester workloadTesters can do Exploratory TestingRegression TestsRequirements can be generated from Tests
- 45. Acceptance Test ApproachesAcceptance Test Driven Development (ATDD)Behavior Driven Development (BDD)Given [some precondition]When [some event]Then [some result]36
- 49. Scripting ApproachesScript logs into each box and runs deployment script commandsScript runs locally, each remote machine has agent execute scriptPackage app using platform’s packaging technology, and use infrastructure management tools push new versions40
- 50. Database DeploymentsVersion your DatabaseEvolve Your Database Incrementally41
- 51. Environment ManagementVersion your Application ConfigurationVersion your Operating System42
- 52. 43Deploying to the Cloudhttp://flic.kr/p/4R35Dd
- 54. Build PipelinesA Build Pipeline is an automated manifestation of your process for getting software from version control into the hands of your users.45
- 55. SynonymsBuild PipelineDeployment PipelineContinuous Integration PipelineDeployment Production LineLiving Build46
- 56. BuildPipelinesA Chain of Jobs Early Jobs run FastEvery Check-in creates a new PipelineWhen a Job Fails, the Pipeline failsKeep Code Production Ready47
- 57. 48Stages of a Pipeline
- 58. 49Pipeline PracticesBuild Once, Deploy ManyDeploy the Same Way to All EnvironmentsSmoke Test you DeploymentsDeploy into a Copy of ProductionEach Change should Propagate InstantlyIf any part fails, Stop the line
- 59. 50Pull System
- 61. AgendaStoryWhat is Continuous Delivery?Core PracticesTools52
- 69. 60Testing Tools
- 71. 62Questions
Editor's Notes
- Requirements/Design/Development Feedback Loop is months.So much can change in that timeFeedback Loop for Release is just as long.
- Continuous delivery is a……set of practices and principles aimed at building, testing and releasing software faster and more frequently.
- 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.
- Agile fixes the feedback loop problem for Requirements/Design/Development.Release Feedback is still months.
- 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.
- The Last Mile tends to be an obstacle to achieving thisTransition – why are automated deployment so important? Because a feature doesn’t add value until it is in production.
- Does anybody know what this is a picture of?