Copying JUnit/XML results from remote host to local build directory?

[Andrew Ceponkus]

Do I need to use a custom script/SSH task to copy *.xml results that are generated on a remote test target in order to make use of the standard JUnit test results/parsing task?  Are there better/alternative ways to use remote-host (via a build-configuration variable) output XML within a build plan?

[Krystian Brazulewicz]

Andrew

I'm not sure what do you mean by remote test target? Does it mean that your build agent (running on host X) runs tests on a different host Y? If this is the case then SCP task might copy the output files for you.

The alternative could be running the build agent on the same host where tests should be executed. In such case copying test results will not be needed.

[Andrew Ceponkus]

Thanks Krystian, unfortunately using an agent on the (non-build) target (ie. an existing VM outside of the elastic pool) wasn't an option, and the built-in on-demand SCP task provides agent --> target transfers only.  

I decided to go with a simpler solution (for now) -- retrieve remote files to associate with the build plan run using a stripped-down web server running on-target, copying files I need to a public docroot (ssh), then finally copying to the build-agent host.  The files are stamped with a unique run identifier, and cleaned-up after the run is complete.