I'd like to add my voice to the support for modifying MSDeploy to issue return codes for failed deployments. I have a situation where the output of MSDeploy does not indicate a failure, but the deployment was incomplete. If I point MSDeploy at a servernot running the Web Deploy service I get the following:
command output:
e:\build\agent1\RWS_Test_Web_Build\Microsoft_Deploy_Web_App\trunk>"C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe" -verb:sync -source:package=TestVS10XML.zip -dest:auto=computerName=ad1hfdadm801,includeAcls=False -disableLink:AppPoolExtension -disableLink:ContentExtension -disableLink:CertificateExtension -setParamFile:"TestVS10XML.SetParameters.xml"
Info: Adding ACL's for path (Default Web Site/TestVS10XML)
Info: Adding ACL's for path (Default Web Site/TestVS10XML)
Total changes: 2 (0 added, 0 deleted, 2 updated, 0 parameters changed, 0 bytes copied)
e:\build\agent1\RWS_Test_Web_Build\Microsoft_Deploy_Web_App\trunk>exit /b 0
===============================
command exit code: 0
None of the files were moved bu no errors were issued. Given this is part of an enterprise deployment tool I can't scan the output for whatisn't there. If there were error messages that might be a different story but there aren't. We need a comprehensive set of return codes for which we can test so that including MSDeploy commands in deployment scripts can be tested for success or failure.</div>