Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
App Service Deploy task fails due to incorrect isMSDeployPackage implementation #6946
The vsts task "Azure App Service deploy" fails when a correct web deploy package has been provided. The error "Error: Source (Manifest) and destination (ContentPath) are not compatible for the given operation" will show up due to the following (generated) msdeploy command:
The function below checks whether or not the provided web deployment package is valid:
It fails when there is no parameters.xml or systeminfo.xml. Due to its implementation, this check is case sensitive: when there is a SystemInfo.xml instead of systeminfo.xml, the function returns false and the command as shown above will bug out.
The proposed solution is to at least include "SystemInfo.xml", but preferably make this check case-insensitive.
a temporary workaround is to create a new msdeploy package. In my case, this leads to extra work, as this package has been provided by a 3rd party.
@arjgupta you added this logic with this PR https://github.com/Microsoft/vsts-tasks/pull/3549/files#diff-a2b5b3ac78f6bfd42fd129f5a0d20787
Any reason why you went with only 2 case-sensitive cases?