The document discusses continuous delivery, outlining its principles and core practices aimed at enhancing software development efficiency. It contrasts traditional waterfall methods with agile approaches to highlight the benefits of continuous integration and deployment, emphasizing the importance of automation and collaboration. Key components include build pipelines, testing strategies, and deployment automation to enable faster and more reliable software releases.

1. Continuous DeliveryMike McGarrmike.mcgarr@excella.comhttp://earlyandoften.wordpress.com @jmichaelmcgarr

2. About MeJ. Michael (Mike) McGarr

3. Excella Consulting, Arlington VA

4. Lead of Excella’s Java Center of Excellence

5. Java Developer for over 11 years

6. Interests:

7. Developer Productivity

8. XP & Agile

9. Automation

10. Testing

11. Polyglot Programming2

12. AgendaStoryWhat is Continuous Delivery?Core PracticesTools3

13. Typical Project4Analyst & CustomerRequirementsArchitectDesignDeveloperDevelopmentTesterQAOperationsRelease

14. 5Waterfallhttp://flic.kr/p/6fREaa

15. 6Problems with WaterfallLong QA feedback loopLack of collaborationInability to change direction

16. WaterFall Project7Analyst & CustomerRequirementsArchitectDesignDeveloperDevelopmentTesterQAOperationsMonths!Release

17. 8Agilehttp://flic.kr/p/PQFQg

18. Agile Project9Customer & TeamCustomer & TeamCustomer & TeamRequirementsRequirementsRequirementsTestTestTestDevelopmentDevelopmentDevelopmentOperationsReleaseDays!TheLast Mile?Months!

19. 10The Last MileManual DeploymentsInsufficient Configuration ManagementInfrequent, Error Prone Deployments

20. 11Stressful Releases

21. AgendaStoryWhat is Continuous Delivery?Core PracticesTools12

22. 13What isContinuous Delivery?

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

27. GoalsCycle TimeQuality18

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

29. http://flic.kr/p/y8KV820Done means Released

30. 21Frequent Automated Deploymentshttp://flic.kr/p/29Ree

31. 22Continuous what?ContinuousDeliveryContinuousDeploymentContinuousIntegration

32. AgendaStoryWhat is Continuous Delivery?Core PracticesTools23

33. 24Core Practices

34. 25Continuous DeploymentBuild PipelinesDeployment AutomationConfigurationManagementContinuous IntegrationTestingAgile

35. 26Configuration ManagementVersion Everything!Single Identifier DependenciesApp ConfigurationsDataEnvironments

36. 27Continuous Integrationhttp://flic.kr/p/5GpzSM

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

46. http://flic.kr/p/6VmGxK37Deployment Automation

47. 38Deployment AutomationArtifactRepositoryApplicationConfigurationsMiddlewareVersionControlOperating SystemDatabase

48. 39Use Appropriate Technologyhttp://flic.kr/p/6pmtQL

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

53. 44Build Pipelineshttp://www.fotopedia.com/users/chmehl

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

60. 51Continuous Deployment

61. AgendaStoryWhat is Continuous Delivery?Core PracticesTools52

62. 53Toolshttp://flic.kr/p/5cK2

63. Version Control54

64. Dependency Management55

65. Database Management56

66. Infrastructure Management57

67. 58Continuous Integration

68. 59Build Automation

69. 60Testing Tools

70. 61Acceptance Test Tools

71. 62Questions

72. 63Contact MeMike McGarrmike.mcgarr@excella.comhttp://earlyandoften.wordpress.com@jmichaelmcgarr