When collecting artifacts, can TC follow softlinks to directories?
To save copying, I am using soft links to link run directories into my artifact directory, with the hope that TC will recurse the softlink and include the run directory contents in the artifacts that it saves. However I find that the links are ignored, and I have to copy the run directories themselves into the artifacts directory in order for TC to save them as artifacts.
From another post in this forum it seems that softlinks to files should work, however I would like for this softlink to a directory to work. I've tried both absolute and relative paths for the link.
Is this expected to work?
Please sign in to leave a comment.
A bit late, but as I understand, by a run directory you mean the build checkout directory. While creating a symlink in the artifacts storage to a file or folder in the build checkout directory can "work" in some special cases, i.e. file system of the build agent is available from the build server, that is something I would strongly recommend avoiding.
While you will be able to hack around publishing the artifacts, the build checkout directory's content tends to be overwritten frequently, its location may change, and it is also agent-specific meaning the symlink will somehow need to point to the checkout directory of the specific agent. Additionally, such an approach will have problems with keeping the history of the artifacts.