Creating .7z artifacts much slower than .zip artifacts and no smaller

In my release build configuration I gather all the .pdbs into a zipped file using the Artifacts Path setup on the build configuration:

Originally I had this set up to produce a .zip file which was coming out at over 100MB.
I had manually unzipped the .zip file and rezipped it as a .7z and it came out at just over 2MB so I thought I'd change my configuration to produce .7z files to save disk space.

Unfortunately, the new .7z artifacts are still over 100MB, and I only seem to get the 2MB size if I manually 7zip the files.
The other problem is that the publishing of the artifacts has gone from under 2 minutes for the .zip artifacts, to about 35 minutes for the .7z artifacts.

The difference between the two configurations that I've used is literally changing this:

**/bin/Release/*.pdb =>  MyPdbs_%system.MajorRevision%.%system.MinorRevision%.%system.BuildNumber%.%build.vcs.number.MyRepo%.zip

to this:

**/bin/Release/*.pdb =>  MyPdbs_%system.MajorRevision%.%system.MinorRevision%.%system.BuildNumber%.%build.vcs.number.MyRepo%.7z

I've tried doing the equivalent operations locally on command line, and manually, and the time taken  and size is roughly the same for both, but both smaller and quicker than what  TeamCity is doing.

If TeamCity would produce .7z files of the less than 5MB size that I expected, I could live with the slow publishing step.
So is there a way I can get it to produce files of the size I expect?
And is there any way to speed it up?

2 comments
Comment actions Permalink

Hello,

Here is the related issue https://youtrack.jetbrains.com/issue/TW-39660, please watch/vote for it.
Current workaround is to archive artifacts inside the build script e.g in the last build step and then list the prepared files in the artifact publishing field.
Also you can try to use .tar archives.

0
Comment actions Permalink

Oh REALLY BUT I DONT THINK SO, SO CAN YOU PLEASE ELABORATE ME MORE. SO I CAN USE THIS INTO MY PROJECT OPEN APK FILE. THANKS

0

Please sign in to leave a comment.