Hi,
A deployment setup I created (and re-created to verify) does not use the destionation subfolder.
The indicated subfolder is not present in the json, but I guess the deployment is using additional folder 1 - subfolder “Development”.
{
“scheduled”: false,
“label”: “Replace Dev”,
“deployments”: [
{
“name”: “Replace Dev”,
“source”: {
“type”: “otto4jit”,
“buildOptions”: {},
“auth”: {
“type”: “apiKey”,
“apiKey”: “***”
},
“serverUrl”: “https://•••••”
},
“fileOperations”: [
{
“target”: {
“fileName”: “•••• Dev.fmp12”
},
“operation”: “replace”,
“source”: {
“fileName”: “••••.fmp12”
}
}
],
“options”: {
“closeFilesAfterBuild”: false,
“keepFilesClosedAfterComplete”: false
}
}
],
“abortRemaining”: false
}
The file is installed in Additional Folder 1, but not the subfolder.
The RC_Data folder is created, but the RC_Data files in production are not installed, I wonder if this is to be considered a bug or not, but since a build is made, I would expect the complete solution to be backed up, and not just the file, or that it would be an option to do so.
So sorry, two topics in one message, but maybe this second thing is related.
Don’t know since I never checked this with other customers, since I have rsync routines in place.