You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Build Validation Scripts utilize ANSI escape codes in the summary section in order to render text with color in terminals that support it. While this is visually pleasant and a reasonable default, not every environment attempts to render color when these codes are encountered. Instead, they are printed as plain text, leading to visual clutter. Notably, Jenkins console logs do not support these escape codes (without plugin support):
To solve this, it would be nice if there were a way to disable these escape codes and just print the plain text output.
The text was updated successfully, but these errors were encountered:
@erichaagdev I think this could be easily achieved by adding a CLI argument, that when set, causes the color code constants to be set to empty strings.
We could also switch to plain text mode when running with the fail if not fully cacheable flag as the main use case there is for running in CI. Unfortunately, that wouldn't for experiment 1 since it doesn't have that flag.
The Build Validation Scripts utilize ANSI escape codes in the summary section in order to render text with color in terminals that support it. While this is visually pleasant and a reasonable default, not every environment attempts to render color when these codes are encountered. Instead, they are printed as plain text, leading to visual clutter. Notably, Jenkins console logs do not support these escape codes (without plugin support):
To solve this, it would be nice if there were a way to disable these escape codes and just print the plain text output.
The text was updated successfully, but these errors were encountered: