Continuous Deployment to Build Trust

Transcript

1. Continuous Deployment to Build Trust CHRIS WELDON SENIOR CONSULTANT IMPROVING ENTERPRISES
2. Chris Weldon  Senior Consultant  Microsoft MVP  Slings Code in C# and PHP  Systems Administrator devops  chris@chrisweldon.net  @neraath
3. And now for something completely different
4. As a conference presenter, I would like a web site with upcoming conferences, so I can stay in-the-know on the conference circuit.
5. As a conference presenter, I would like to see a list of upcoming conferences, so that I know what to submit presentations for.
6. Our Journey Current Continuous Deployments
7. In Business
8. We Develop Software
9. When developing software…
10. We often try as a team…
11. But are often racing the clock…
12. So we rush Apps to Production.
13. This cycle repeats and we make Frequent Changes to Production.
14. And Our Apps Repeatedly Break
15. When stuff breaks… The business gets mad!
16. They start to see us as “rogues”
17. And institute gates to stop this “bad” activity
18. Gates are typically nothing more than
19. Why?
20. It’s about Trust.
21. How do we rebuild trust?
22. Back to basics.
23. We write software to support the business.
24. Or software is the business.
25. We need to adapt to changes in business needs.
26. We need to (rapidly) fix bugs.
27. We properly test first.
28. In order to maintain stability…
29. …we should have slow, continuous evolution of features.
30. So how do we support these goals?
31. Strive for technical excellence!
32. Remember to test!
33. We should constantly integrate all changes back into mainline.
34. requent Deployments Amount of Change Inf F
35. Automate Deployments
36. Our Journey Current Continuous Deployments Automation
37. Technical Excellence
38. Let’s talk about your databases…
39. As a conference organizer, I would like conferences I create to persist beyond my session so that other users can see upcoming conferences.
40. Is your DBA’s idea of SQL Management pitching him a SQL script to run?
41. That’s not automation.
42. Solution: Migrations  Entity Framework Code-First Migrations  Migrator.NET  RoundhousE  And many more…
43. Migrations Demo Demo
44. Configuration Management
45. Scenario: Multiple web applications  CritterMatch.com  Developer Workstations  Integration/QA  Staging  Production  CritterMatch Business Services  Developer Workstations  Integration/QA  Production – Client A  Production – Client B
46. Configuration Management  Configurations likely to change:  Database Connection Strings  Web Service Connection Endpoints  Authorized Users?  Requirements Management  Different views or behaviors  Dependency Injection?  Often times a configuration change, too.
47. Configuration Management Strategies
48. Logging and Monitoring Strategies
49. Better Know a Framework
50. Deployment Techniques
51. Continuous Deployment = Release to Production After Every Commit?
52. We don’t want to be rogues…
53. Production Push/Pull
54. CI Push
55. But how do we establish trust?
56. Our Journey Current Continuous Deployments Automation Testability
57. Unit Tests?
58. What about your UI?
59. What about dependency or component failure?
61. Smoke Tests!
62. Behavioral/Acceptance Tests
63. Still having trust issues?
64. Our Journey Current Continuous Deployments Automation Testability Manageable
65. Gated deployments
66. Rollback Techniques
67. Our Journey Current Continuous Deployments Automation Testability Manageable
68. Recap
69. Q&A
70. Ratings, Please! http://spkr8.com/neraath