The output of our Linux build configurations contains a number symbolic links in the form (e.g. libXXX.so is a symbolic link to libXXX.so.1) . In the artifacts path setting of our build configuration we have "deploy/XXX => linux-XXX.tar.gz". Unfortunately, the resulting tar.gz file contains copies of the files rather than the links themseleves.
Is there anway to tell Teamcity not to follow the links when publishing the artifacts?
I don't know if the tar command used by TeamCity is configurable, but it appears that they went out of their way to copy in the files. I suppose the thinking was that if a symlink points to a location outside of the tree being archived, you'd miss the contents.
I think that you might be better off running the tar command in your build script. By default, tar will store symlinks as is.
