Make WebDeploy transactional
When deploying a site, the previous version should continue to run. If the deployment fails, the site should continue to run on the previous version. If it succeeds, the switch should happen after publication is complete.
Alexandr Marchenko commented
I was pretty sure it is, it is time to automate deploy, got my hands on web deploy and ... without transactional deploy it is not a thing for mission critical apps :(
essamri b. commented
I agree. I have seen some programs meeting my needs during 5 minutes and others not matching with my profile during hours. I was very happy in the begining to discover so many new Tools. I show them 5 minutes and didn't even have the opportunity to try them. In place of that, i was invited to click during 30 minutes to unstall the wifi or to fool in documents about me; when i finished to enter the informations, i discovered everything erased. i had to do it a second, a thirt time, till i refuse. What it the aim of all this type of work that are particularly time-consumming.
Thibault Nélis commented
@Nick Lechnowskyj: I think this is about recovering from problems that would happen during deployment itself, not problems in the application. Supposedly it would also be the answer to this question, although I kind of always hoped there were an answer to that already.
Nick Lechnowskyj commented
@Bertrand, I disagree, It's not web deploys job to give you the ability to test the new version as a staged version before flipping some magical switch, that's what the test server is that you're deploying to is for.
Gaurav Pandey commented
Thank you for the feedback! We will review this for a future version of WebDeploy.
Bertrand Le Roy commented
Bonus points for:
The ability to roll-back in case something is noticed wrong after the switch.
The ability to test the new version as a staged version before flipping the switch manually.