Details
Description
I'm running a remote build which uses TestNG and Selenium to generate test results using a remote Bamboo agent on WindowsXP. On the remote agent, the build runs as expected and the reports (and directory structure) are created with no issues.
I have an artifact copy pattern which will recursively match the contents of the reports directory, so that I can review all of the reports after the build process (Bamboo parses some of these reports as well). My fileset is as follows:
Label: Reports
Directory: testrun
Pattern: */
(on a side note, I also tried *** as the pattern)
When the artifact processor runs, the contents of the directory are matched as expected on the remote agent, but when the artifacts are copied to/recreated on the Bamboo server, the Windows directory separator is retained, so no directories are created and instead files are written out to the root of the download-data/artifacts/build-nn/Reports directory in the form "directoryname\filename.ext".
For example, here is an abbreviated directory listing on the server:
Smoking\add-1node.html
Smoking\add-1node.properties
Smoking\add-1node.xml
Smoking\classes.html
...
testng-failed.xml
testng-results.xml
testng.css
The expected behavior here is that the directory "Smoking" would be created, and then the appropriate artifacts copied into it.
This also causes problems within the Bamboo UI, as I cannot browse through my report artifacts for a completed build as the expected directory structure does not exist.
Attachments
Issue Links
- is duplicated by
-
BAM-2685 Artifacts don't respect differing path separation characters on Windows and Unix
- Closed