I created a new simple workflow that will deploy files from one TS server to another along with the file's external attributes. The instantiation form allows the user to enter the target path (branch/workarea) on the target server where the file should be deployed. During testing, one of my coworkers misunderstood the value of the target path and entered a target path that included subdirectories within a workarea. This caused the target path to be misconfigured in the deployment config. The result was this:
LIB: 2016-01-04 13:19:17 DEPLOYING - [/iwmnt/default/main/Southwest/SWA/WORKAREA/shared/sites/mobile] to [/iwmnt/default/main/Southwest/SWA/Vision_Release/WORKAREA/shared/swa-resources/images/globalnav/ads/sites/mobile]
There were no files to deploy - this is a filelist deployment and the filelist was empty, so it deployed no files, which I expected. However....
This path on the target server existed prior to this deployment: /iwmnt/default/main/Southwest/SWA/Vision_Release/WORKAREA/shared/swa-resources/images/globalnav/ads
And this path did not exist on the target server prior to the deployment: /iwmnt/default/main/Southwest/SWA/Vision_Release/WORKAREA/shared/swa-resources/images/globalnav/ads/sites/mobile
***Notice sites/mobile hadn't existed on the target server
After the deployment, this path now exists: [/iwmnt/default/main/Southwest/SWA/Vision_Release/WORKAREA/shared/swa-resources/images/globalnav/ads/sites/mobile
To summarize, we ended up with a deployment definition that attempted to deploy an empty filelist from a source folder to a target folder where the path existed except the last 2 subdirs, and althougfh no files were deployed, it created those subdirs on the target.
I assume that's the expected behavior for OpenDeploy to create that target path if it didn't already exist. I'm not sure if I agree or disagree with that behavior. My question is - can I turn that specific behavior off in a config somewhere? Specifically just that if a target path does not exist and there are no files to deploy, I don't want it to create that folder on the target? Not sure of this all makes sense. I can try and explain better if it doesn't.
