Is there a deploy tool (or set of tools) that supports rollback of a deployment?

I don't know of any Microsoft-centric, automated provisioning/deployment tools like Capistrano. Here are some tools I've heard of, but never used.

I don't know of any Microsoft-centric, automated provisioning/deployment tools like Capistrano. Here are some tools I've heard of, but never used: MSDeploy, for deploying web application. Microsoft Deployment Services, for managing operating system configuration Microsoft's System Center Configuration Manager BladeLogic HP's Operations Center Up until about three months ago, we did our deployment/provisioning using custom MSBuild scripts.

After a server is provisioned, deploys happen automatically using Robocopy to copy files to a share on the application server, updating changed application binaries and markup files. We've never had a need to rollback any of our deployments, but since our scripts are custom, we could write the logic if we needed to. MSBuild is a terrible deployment/provisioning language.

For the past three months, we've been writing all new scripts in, and porting existing ones to, PowerShell. It is wonderful. With version 2, there is support for running commands on remote servers, like SSH.

We haven't used that functionality yet, but I'm looking forward to pushing setup scripts to remote server to provision and deploy at the same time.

Of course! My favorite is Capistrano. This was originally built for Ruby but I've found that it works just as well for other languages.

Https://github. Com/capistrano/capistrano.

Hmm. Updated the question. Wouldn't capistrano require me to open the Windows Server up to SSH?

I don't know much about SSH. – jcollum May 14 at 2:14 Yes, but what are the alternatives, FTP? Any deployment framework will need some kind of terminal access to the server.

However, deploying Capistrano from a Windows box would probably mean installing Cygwin and PuTTY. I would look for pure Windows alternatives first. – Matthew Ratzloff May 14 at 2:30.

We have been using Git to do our deploys for the last 6 months. Here is the whole process: CI server build the project CI server checks it in to a local git repository CI server pushes the changes to the centralised git repository User creates an empty repository on the live server User adds the central git repository to the remotes User pulls the latest version over https (no need to open any ports) It is a lot to setup in the beginning but once setup it works great. Deploys take seconds as only changed files get copied.

Another great thing about this method is that git keeps history of changes so rolling back is pretty simple. You can also roll back a few revisions and it's done straight on the live server. If something goes wrong reverting is super fast.

Also you can save some time if you use a hosted git service (github) for your central repository. This is a very brief description but I can give you more info if you want.

– jcollum May 17 at 17:23 Currently I don't need to because most sites we do use a 3rd party cms that handles the database. – marto May 17 at 17:38.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.