We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Automated release management with TeamCity & OctopusDeploy

Formal Metadata

Title
Automated release management with TeamCity & OctopusDeploy
Title of Series
Number of Parts
150
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
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.