Many of us have one or more manual steps in our deploy and release processes. This leads to a lot of time spent waiting for the right people to do the job. Also, errors often occur due to steps forgotten or done incorrectly. This often leads to high walls between the testers, IT-ops and the developers.
This talk will start out with some general continuous delivery, the why's, where you'll get to know the actual benefits of applying continuous delivery and the arguments you need to be allowed to spend time on it. Then we will move over to the how's. By demonstrating how you can use TeamCity and OctopusDeploy to configure automated builds and one-click deployment of both an asp.net website and a windows service, and how you can migrate your current manual process into an automated one. Along the way, we will be discussing how OctopusDeploy chooses solves specific problems, and other ways you might handle those issues.
Deploying a service
Deploying a website
Writing PowerShell deployment scripts
The NuGet package format
Using the OctopusDeploy web api
Rolling back failed deployments
Strategies to move from manual to automated/one-click deploy
Connecting the issue tracker