Deat xrootd developers,
Some of CI workflows are deploying code using `xrdcp --recursive` to a target eos folder.
Few days ago, my deployment stopped working because it looks like xrdcp --recursive is not creating subdirectories on the target anymore,, but instead, it flattens the source directory tree and puts all the files in the base target directory not creating any directory on remote.
Currently I am getting these reports from the xrdcp recursive output (4.12.1-1):
```
Source: file://localhost/builds/cta/eoscta-web/public/assets/images/2017-07-06-cern-bulletin.png
Target: root://eoshome.cern.ch:1094//eos/project/c/cta/www/eoscta_1744989git5896d493//2017-07-06-cern-bulletin.png
```
While the same command used to do this (4.11.3-1):
```
Source: file://localhost/builds/cta/eoscta-web/public/assets/images/2017-07-06-cern-bulletin.png
Target: root://eoshome.cern.ch:1094//eos/project/c/cta/www/eoscta_1647172git504d753f//public/assets/images/2017-07-06-cern-bulletin.png
```
That was the correct behaviour.
This is what I am running:
```
xrdcp="/usr/bin/xrdcp"
$xrdcp --force --recursive $CI_OUTPUT_DIR/ root://eoshome.cern.ch/$EOS_PATH/ 2>&1 >/dev/null
```
on the following arguments:
```
CI_OUTPUT_DIR=public EOS_PATH=/eos/project/c/cta/www/eoscta_${EOSCTAWEB_ID}
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/1227
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
