Reduce log output for package builds
Job logs for Omnibus package builds are fairly large. This one from an auto-deploy build today is 1MB.
- If we remove 455 lines of output from this warning, we're down to ~950 K.
-
If we update this call to add, we're down to ~713 K. => !4737 (merged)--no-progress
(or--quiet
or--only-show-errors
) so that we don't show messages likeCompleted 876.0 MiB/877.0 MiB (109.9 MiB/s) with 1 file(s) remaining
- If we can reduce the log level from
INFO
toWARN
(maybe just for auto-deploy builds?) we're down to ~626 K.
At this point, the log would look like this: https://gitlab.com/-/snippets/2034054
What jumps out to me in the logs at this point is that we're checking out a fresh repository and then pulling the omnibus-gitlab repository, which brings in almost 6,000 tags and branches as "new" refs. Why is the repository not cached at all? Without those we'd be down to ~139 K.
Edited by Robert Speicher