Artifact Path problem when using absolute path with wildcards
Hello,
I have recently upgraded to TeamCity Enterprise 2017.2.4 (build 51228) and I am having trouble with some of my build artifacts not being found. Prior to the upgrade this was working fine. It seems this this only happens when using a network artifact path and a wildcard.
i.e.
This works (the artifact is successfully found and published):
\\PC123\Projects\Build_844\filename.txt
This does not work (No files found):
\\PC123\Projects\Build_844\*.txt
Is this a known issue?
Thanks,
Alex.
Please sign in to leave a comment.
Hi Alex,
could you please share the exact error message? I'm unaware of such an issue, so I would like to ask first to verify that it's a consistent problem and not a specific sutiation. If you can confirm it doesn't work, it would be useful to open a request in our issue tracker and include the full build log. If it used to work but it doesn't anymore, it might be a regression, so it would also be useful to know which version you were running before upgrading where it worked.
Our tracker: https://youtrack.jetbrains.com/issues/TW
Error we receive as follows:
[15:12:50] [Publishing artifacts] Collecting files to publish: [\\servername\e$\DatabaseTemp\*.bak => DatabaseBackups]
[15:12:50] [Publishing artifacts] Artifacts path '//servername/e$/DatabaseTemp/*.bak' not found
Created TeamCity support ticket: https://youtrack.jetbrains.com/issue/TW-56065