Audit GitLab QA & QA Tests logs
auditing what we should log to debug and what to info, logging everything to debug level just doesn't make sense from normal logging practices.
from gitlab-org/gitlab!81442 (comment 853161410)
Now that we have standardized logging in place, it would be beneficial to review existing logging points and assess if their level is correct.
There are a few warn
in the test code which should be logged as well.
Potential improvements:
-
Audit log messages and adjust log levels. Resource fabrication should probably be logged to info
, leave low level selenium stuff indebug
-
Log to file debug
level messages and store as artifact. Useinfo
level to log to stdout so we do not spam our runners constantly going over the max limit and forced to look at logs in plain text -
Stream shell command (docker etc.) output through logger so the output can also be logged at different levels -
Update all pipeline configurations to use new logging strategy
Edited by Andrejs Cunskis