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.

1. Continuous Delivery Mike McGarr mike.mcgarr@excella.com http://earlyandoften.wordpress.com @jmichaelmcgarr

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. Agenda Story What is Continuous Delivery? Core Practices Tools 3

13. Typical Project 4 Analyst & Customer Requirements Architect Design Developer Development Tester QA Operations Release

14. 5 Waterfall http://flic.kr/p/6fREaa

15. 6 Problems with Waterfall Long QA feedback loop Lack of collaboration Inability to change direction

16. WaterFall Project 7 Analyst & Customer Requirements Architect Design Developer Development Tester QA Operations Months! Release

17. 8 Agile http://flic.kr/p/PQFQg

18. Agile Project 9 Customer & Team Customer & Team Customer & Team Requirements Requirements Requirements Test Test Test Development Development Development Operations Release Days! The Last Mile? Months!

19. 10 The Last Mile Manual Deployments Insufficient Configuration Management Infrequent, Error Prone Deployments

20. 11 Stressful Releases

21. Agenda Story What is Continuous Delivery? Core Practices Tools 12

22. 13 What is Continuous Delivery?

23. 14

24. 15

25. …a set of practices and principles aimed at, building, testing, and releasing software faster and more frequently. 16 Continuous 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 Manifesto 17

27. Goals Cycle Time Quality 18

29. http://flic.kr/p/y8KV8 20 Done means Released

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

31. 22 Continuous what? Continuous Delivery Continuous Deployment Continuous Integration

32. Agenda Story What is Continuous Delivery? Core Practices Tools 23

33. 24 Core Practices

34. 25 Continuous Deployment Build Pipelines Deployment Automation Configuration Management Continuous Integration Testing Agile

35. 26 Configuration Management Version Everything! Single Identifier Dependencies App Configurations Data Environments

36. 27 Continuous Integration http://flic.kr/p/5GpzSM

37. 28 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

38. 29 Recommended Practices Extreme Programming (XP) Fail a Build for Design Breaches Fail a Build for Slow Tests Fail a Build for Warnings & Code Style Breaches

39. 30 Testing

40. 31 Kinds of Tests Unit Tests Integration Tests Functional/Acceptance Tests Performance & Load Tests Penetration Tests Exploratory Tests

41. 32 Testing Strategy Identify and Prioritize Project Risk Decide what Actions to Take Tests = Executable Specifications Confidence

42. 33

43. 34 Testing Recommendations Automate your Tests Use Fakes/Mocks Automated Acceptance Testing

44. 35 Automated Acceptance Tests Fast Feedback Reduce Tester workload Testers can do Exploratory Testing Regression Tests Requirements can be generated from Tests

45. Acceptance Test Approaches Acceptance Test Driven Development (ATDD) Behavior Driven Development (BDD) Given [some precondition] When [some event] Then [some result] 36

46. http://flic.kr/p/6VmGxK 37 Deployment Automation

47. 38 Deployment Automation Artifact Repository Application Configurations Middleware Version Control Operating System Database

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

49. Scripting Approaches Script logs into each box and runs deployment script commands Script runs locally, each remote machine has agent execute script Package app using platform’s packaging technology, and use infrastructure management tools push new versions 40

50. Database Deployments Version your Database Evolve Your Database Incrementally 41

51. Environment Management Version your Application Configuration Version your Operating System 42

52. 43 Deploying to the Cloud http://flic.kr/p/4R35Dd

53. 44 Build Pipelines http://www.fotopedia.com/users/chmehl

54. Build Pipelines A Build Pipeline is an automated manifestation of your process for getting software from version control into the hands of your users. 45

55. Synonyms Build Pipeline Deployment Pipeline Continuous Integration Pipeline Deployment Production Line Living Build 46

56. BuildPipelines A Chain of Jobs Early Jobs run Fast Every Check-in creates a new Pipeline When a Job Fails, the Pipeline fails Keep Code Production Ready 47

57. 48 Stages of a Pipeline

58. 49 Pipeline Practices Build Once, Deploy Many Deploy the Same Way to All Environments Smoke Test you Deployments Deploy into a Copy of Production Each Change should Propagate Instantly If any part fails, Stop the line

59. 50 Pull System

60. 51 Continuous Deployment

61. Agenda Story What is Continuous Delivery? Core Practices Tools 52

62. 53 Tools http://flic.kr/p/5cK2

63. Version Control 54

64. Dependency Management 55

65. Database Management 56

66. Infrastructure Management 57

67. 58 Continuous Integration

68. 59 Build Automation

69. 60 Testing Tools

70. 61 Acceptance Test Tools

71. 62 Questions

72. 63 Contact Me Mike McGarr mike.mcgarr@excella.com http://earlyandoften.wordpress.com @jmichaelmcgarr