We're using Microsoft's Release Management to deploy our web application to our test environment (QA). It is a straight-forward MVC.Net web application. Our build generates a web deploy package and we have a command script that sets some parameters based on the target environment (QA is just the first step), and then runs the standard Web Deploy command line tool. The command script works without errors when run from the command line outside of Release Management.
When we move this process into Release Management using the command-line tool, we encounter a timeout during the deploy step of the workflow. The error is:
The installation command \"powershell -command ./RunCommandLine.ps1 -FilePath 'Deployment\Deploy.cmd' -Arguments '/T:QA /E:intranet' -UserDomain 'domain' -UserName 'username' -UserPassword '*****'\" reached the configured timeout (2 minutes); the process was terminated.
We've checked the output log and there is no information from the script at all. We have echo commands in the beginning that should at least dump some output to the log before any action is taken.
The interesting thing is that when we click the "Retry failed deployment" button, the retry succeeds in about 15 seconds without any issues. This happens for each release - fails with timeout, retry succeeds in 15 seconds.
Any ideas from any release management gurus is greatly appreciated.