NTFS hardlinks aware artifact archives - how to?

Our build produces many folders with binaries for different products. Many binaries (think libraries) are identical between folders. Total size of all folders is humiliating - about 15 Gb. BUT knowing that there are a lot of duplicate binaries we use file system hardlinks instead of copying files over and over and this brings our total build size to more manageable 1 Gb. 

The problem is that when TeamCity uses ZIP to send artifacts to the server all those hardlinks are treated as a normal files and therefore the size of the ZIP, time of zipping and network transfer time is like it was 15 Gb.

I wonder if we can replace ZIP with something else (TAR?) which understands hardlinks, preserves them as such in the archive and restores at unpacking time. Is that possible?


Thank you!


Please sign in to leave a comment.