<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=19381) </details> <!--IssueSummary end--> ### Description At the moment, CI creates and uses only ZIP files. These is an very unnative format for Linux and creates some problems: - symbolic links seem to be some extension which is not supported by all implementations. E.g. popular windows clients (7zip) create only some small text files which causes a lot of confusion. - hard links are not supported at all. Might be not a problem for deploy except that archive file is enlarged. But it can cause massive problems for caches when build system uses hard links. There should be used a more native format for the deploy and cache archives, e.g. 'tar'