PreservePaths not working correctly for Azure Web Apps

[slewis74]

Our documentation list an example about Preserving Paths during deployment of an Azure Web App.

The scenario described in the documentation no longer works. If the components are in a common folder and that folder is listed in the Octopus variable then all folders below it are preserved, regardless of any other expressions you add. If you don't list the common folder then it and all of it's children are always removed, even if they are list explicitly to preserve in the expression.

Source http://help.octopusdeploy.com/discussions/problems/53130

[slewis74]

PreservePaths not working correctly for Azure Web Apps

[LukaszPrzybysz]

Hi,
As you've already closed the discussion (http://help.octopusdeploy.com/discussions/problems/53130-preservepaths-doesnt-work-as-expected), can I expect it to be fixed?

Thanks,
Lukasz

[slewis74]

We've talked about this among the team and it seems that the updated behavior in the newer version of WebDeploy actually removes the need to use the expression this way. It was documented as a way of stopping ComponentA from removing the files for ComponentB during deployment. The updated WebDeploy only acts on the files under ComponentA's folder now anyway, so you should just have to list the //components folder on your root level project deployment to stop it removing any of the components.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.