Zip test reports instead of uploading individual files
K
Kenaniah Cerny
I have a test suite that runs in 2 minutes, but takes over 3 minutes to upload test result artifacts. Teach test result file is an XML that's less than 1 KB in size, and these could easily be zipped and uploaded as one file if Circle CI was smarter about it. We've observed an upload latency of roughly 0.5 seconds per file which would essentially disappear if the entire folder was archived & uploaded.
CCI-I-651
j
jonest41@aetna.com
A key goal of any automated build pipeline should™ be fast feedback for introspection of issues. Uploading a report directory allows immediate viewing in the artifacts tab of the "new" ui if you are ok with waiting for upload overhead, potentially burning credits for a purely I/O blocked workload. The workaround is: create a zip, archive the zip, download the zip, extract the zip, inspect the data, and finally clean up the mess that was just made. This is a UX fail at every level. So many extra steps slowing people down.
K
Kenaniah
This would be extremely useful in reducing run times overall. I also have test suites that execute in a fraction of the time it takes Circle CI to finish uploading the test results. Why isn't this a higher priority?
A
Antoine Bolvy
Was also discussed here https://discuss.circleci.com/t/uploading-artifacts-recursively-is-exceptionally-slow/14558, with seven likes and 3 people commenting, so more votes should be taken into account.
Nicolas Caniart says:
Would you have ways to go around this ? Building an archive with the files isn’t good enough: it renders the files too cumbersome to access.
So the ideal feature request would be that the recursive folder uploads create an archive for upload transparently, and that the files are still available individually in the artifacts tab.