Continuous Delivery for .Net on AWS with Octopus Deploy @ Domain.com.au Initially presented at Sydney's Continuous Delivery Meetup on the 17th of September 2014

1. .Net Continuous Delivery
Presented by Jason Brown & Fabien Ruffin

2. Background
• Transition to Agile
• Growing team
• Migration from monolithic application to microservices

3. What we will cover
•Build process
•Infrastructure automation
•Deployment automation

4. Process Overview

5. Build

6. Build - Overview
• Local build
• Self-contained
• Runs tests
• Quick and easy updates
• Fast builds
• Deploy on commit

7. Build - Solution
• 1 script to run the full process
• PowerShell + psake
• NUnit runner
• OpenCover
• NuGet.exe
• Build script and tools packaged as NuGet packages
• Bamboo triggers deployments

13. Infrastructure

14. The Infrastructure Challenges
• Scalable
• Available
• Reliable
• Secure
• Robust
• Performant
• Deployable
• Manageable
• Plentiful
• Cheap

15. ...so we built a robot army

16. ...actually, a HEADLESS robot army

17. The Cluster Standup Process
• CloudFormation templates
• Standard AWS AMIs
• EC2 Server with 3-stage DSC
• base.ps1 - army config
• cluster.ps1 - platoon config
• cluster-deploy.ps1 - app code
• One-touch process.
• ~10 minutes to provision
• < 10 minutes to autoscale

18. Deployments

19. Deployment
• Custom NuGet Gallery (for multiple private feeds)
• Octopus Deploy
• MS Entity Framework database migrations

20. Typical Deployment Flow
UAT Staging Production

21. Domain’s Deployment Flow
Git Branch Bamboo Branch NuGet Package Id Octopus environment
develop develop develop-{app name} UAT
release release release-{app name} Staging
master master master-{app name} Production

22. Why Octopus?
• Different focus
• Remote deployments
• Automatic parallelization
• Configuration management
• Deployment can be messy

23. Deployment
Notifications

24. Octopus - Deployment

25. No-Downtime Deployment
Web Server (IIS 7+ only)
Live Site/API
New Site/API
Swap bindings

26. Octopus - Notifications

27. Octopus - Configuration Management

28. Monitoring & Alerting

29. Limitations & Next Steps
• 1 web application per cluster only
• Integration and UI/functional test still manually triggered
• Windows-only deployments
• Database auto-deployment only for Entity Framework
• CloudFormation doesn’t support all options for all services

30. Outcome
•No-Ops releases managed by testers
•150 production releases in the last month
•A bug found in the morning is usually patched a few hours later
•Quick builds and deployment allowed a dozen deployments in half a
day to address performance issues