Spaces in Artifact paths

What is the correct way to escape spaces in a Artifact path?

I have 2 identical sets of files outputted from a build one in a subdir with spaces one without. Using the artifact paths below:

lib/UnitTest/Output/WinMobile/Debug/*.exe => UnitTests/WinMobile
lib/UnitTest/Output/Windows Mobile 5.0 Pocket PC SDK (ARMV4I)/Debug/*.exe => UnitTests/Windows Mobile

The first artifact path generates artifacts the second path does not. Output is as follows:

[16:44:42]: Publishing artifacts (6s)
[16:44:42]: [Publishing artifacts] Paths to publish: [lib/UnitTest/Output/WinMobile/Debug/*.exe => UnitTests/WinMobile, lib/UnitTest/Output/Windows Mobile 5.0 Pocket PC SDK (ARMV4I)/Debug/*.exe => UnitTests/Windows Mobile, , teamcity-info.xml]
[16:44:42]: [Publishing artifacts] Publishing artifacts 'lib/UnitTest/Output/WinMobile/Debug/*.exe' to UnitTests/WinMobile
[16:44:46]: [Publishing artifacts] Publishing artifacts 'lib/UnitTest/Output/Windows Mobile 5.0 Pocket PC SDK (ARMV4I)/Debug/*.exe' to UnitTests/Windows Mobile
[16:44:49]: [Publishing artifacts] Artifacts path lib/UnitTest/Output/Windows Mobile 5.0 Pocket PC SDK (ARMV4I)/Debug/*.exe not found
[16:50:58]: Build finished


If I look at the working directory on the build agent the files in ib/UnitTest/Output/Windows Mobile 5.0 Pocket PC SDK (ARMV4I)/Debug definately exist.


Thanks,
Nic
2 comments
Comment actions Permalink

The problem is not with spaces but with parenthesis. This is a TeamCity bug which will be fixed in the upcoming 4.5 release. As a workaround try to remove parenthesis from the pattern, for example insert ? characters in place of parenthesis.

0
Comment actions Permalink

Thanks that worked. One problem with the work around is because the path contains a wildcard the artifacts are stored in

UnitTests/Windows Mobile/Windows Mobile 5.0 Pocket PC SDK (ARMV4I)/Debug/

not

UnitTests/Windows Mobile

Is there a way to avoid this? Looking foward to 4.5!

0

Please sign in to leave a comment.