IIS Web App Deployment Using WinRM Version 1.6.4 Breaks MSDeploy Additional Arguments
cookontherun opened this issue · 7 comments
Using TFS/DEVOPS and have multiple builds that stopped working yesterday after the IIS Web App Deployment Using WinRM extension update was pushed to our server. I don’t see a way to rollback this extension to the earlier version. The additional arguments feature of the build task does not pass the argument now to the MSDeploy command line:
How can we get these -skip:file command line parameters to be included in the MsDeploy command line:
Same issue.. it doesn't take into account "AdditionalArguments" parameter which is used to skip files or test the deployment with "-whatif". What a surprise today after the deployment ! 😃
Hi @cookontherun and @Carlos-724 I apologize for the inconvenience.
I already work on the fix.
@cookontherun can you please provide the task version, that you use.
Hi @LeftTwixWand, I'm having the same issue on both versions: 2.1.3 and 1.5.3.
@LeftTwixWand sorry to post as well but this almost broke our production environment. Lucky I saw this happening first in our test environment so I could stop our continuous deployment to production. Hope you can fix this asap and possibly prevent such things happening in future releases.
Hey @cookontherun, @Carlos-724, @KevinCar98, @RicardoLans once again I apologize for the inconvenience.
We reverted all the changes made in 1.6.4 and will work on its improvement.
Now you can update IIS Web App Deployment Using WinRM to version 1.6.5 and keep working.
Hey @RicardoLans @cookontherun @Carlos-724 @KevinCar98.
Today we released an updated version of IIS Web App Deployment extension with the fix of this issue.
Hope you won't have any issues with our extension in the future.
And thank you all for the feedback❤️