tar output should not be verbose, or should be a switch
Even in a small project, with only 8 (direct) npm dependencies, the impact of running tar with the -v switch is such that the build hits the Build log exceeded limit of 4194304 bytes. error.
This is happening at both the archive creation: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/shells/bash.go#L232 (Can't find where that is actually calling tar)
And the cache unpack (also about 10 lines below): https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/shells/bash.go#L156
Sample output
Following is a sample of the output we're generating, and why it
Archiving cache...
INFO[0001] Creating archive ../../../cache/eventmatrix-platform/intouch-invite/build/ci3/cache.tgz ...
node_modules/
node_modules/husky/
node_modules/husky/package.json
node_modules/husky/.npmignore
node_modules/husky/README.md
node_modules/husky/LICENSE
node_modules/husky/.travis.yml
node_modules/husky/bin/
node_modules/husky/bin/install.js
node_modules/husky/bin/uninstall.js
node_modules/husky/hooks.json
node_modules/husky/src/
node_modules/husky/src/index.js
node_modules/husky/test/
node_modules/husky/test/index.js
node_modules/husky/node_modules/
node_modules/husky/node_modules/normalize-path/
node_modules/husky/node_modules/normalize-path/package.json
node_modules/husky/node_modules/normalize-path/README.md
node_modules/husky/node_modules/normalize-path/index.js
node_modules/laravel-spark/
node_modules/laravel-spark/package.json
...
tors/root.js
node_modules/laravel-elixir/node_modules/vueify/node_modules/postcss-selector-parser/dist/selectors/selector.js
node_modules/laravel-elixir/node_modules/vueify/node_modules/postcss-selector-parser/dist/selectors/string.js
node_modules/laravel-elixir/node_mod
Build log exceeded limit of 4194304 bytes.
Build succeeded.
