Teamcity subversion manual#

Throughout all this I’m going to be working towards the principle of least surprise because in the world of deployments, surprise is rarely a good thing. I want to look at how we can tackle this through a combination of config transforms, website packaging, Web Deploy and finally, automation via TeamCity to both development and production environments.

Teamcity subversion manual#

There are actually two different issues here – configuration management and deployment, the latter being a question of manual versus automated. An urgent release is required but the one person who understands the process (and possibly the credentials), is not contactable.A critical flaw is found in the release and you need to rapidly roll back to the previous version.Network connectivity drops out part way through a deployment leaving half the content in version 1 and the other half in version 2.Development environment connection strings or other app settings are accidentally published to production.Consider the opportunities for things to go wrong under the scenarios described above: What’s so wrong with all these practices? They’re unpredictable and in the world of configuring and releasing applications, predictability is key. Predictability, predictability, predictability But now that they have, the excuses for “deploying it wrong” are running out. Some of the “wrong” scenarios above have only been satisfactorily addressed in the latest generation of tools. To be fair, there really haven’t been a lot of alternatives.

This might seem a little sensationalist but after Scott Hanselman set a high “doing it wrong” bar in his excellent Web Deployment Made Awesome: If You're Using XCopy, You're Doing It Wrong video, he made it pretty clear just how wrong many people have been doing deployment. If publishing involves any manual handling of Web.config, you’re deploying it wrong. If not everyone is following exactly the same release process, you’re deploying it wrong. If you use an FTP client to move your files to a remote server, you’re deploying it wrong. If you manually run an Xcopy command, you’re deploying it wrong. If you publish a web application using CTRL-C and CTRL-V, you’re deploying it wrong. 22 November 2010 Part 2: MSBuild and deployable packages >