| commit | 86cafa64da0fec88610a905addbd6824a88c43ac | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <edtanous@google.com> | Wed Feb 16 16:08:10 2022 -0800 |
| committer | Ed Tanous <ed@tanous.net> | Fri Feb 18 03:23:57 2022 +0000 |
| tree | 25f24558d7c44dd3fca3fafb7416e7f26439587f | |
| parent | 76f25deb2163006c6db4126e1cce256054bc3f56 [diff] |
Disable colored output in shellcheck
shellcheck defaults to using colors in its output. Unfortunately,
jenkins is unable to process bash-style colors in the console log, so in
practice, when colors are used, the jenkins logs end up like:
[1mIn jenkins/userid-validation line 25:[0m
[0mif [ "x${COMMITTER_EMAIL}" == "x" ]; then[0m
[32m ^-------------------^ SC2268 (style): Avoid x-prefix in comparisons as it no longer serves a purpose.[0m
[1mDid you mean: [0m
if [ "${COMMITTER_EMAIL}" == "" ]; then
With lots of control characters. This is annoying to review in build
scripts, which are primarily being read from disk somewhere.
The above log was pulled from the review here:
https://jenkins.openbmc.org/job/CI-MISC/job/ci-openbmc-build-scripts/455/console
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: Ibc827039150f7018b31a63ac11fa7c19776414c9
Build script for CI jobs in Jenkins.