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
Is your feature request related to a problem? Please describe.
A buildkite setup I use has a very long (175 chars) sandboxed path to the build directory, which is printed ~1800 times throughout the build and tests. It makes it hard to quickly parse logs because of wrapping, and that the key relevant detail is a small fraction of the text output.
The paths from within this path are printed from various tools and code paths, and would thus be difficult to tokenize the path at the point of print.
Describe the solution you'd like
A way to replace strings in the log that is displayed in buildkite
Replacing the following strings:
/some/really/long/path/to/my_repo => [my_repo]
...
[my_repo]/contrib/main.sh 733
...
Perhaps raw logs could maintain the original strings?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Thanks for the feature request @IanButterworth! The string replacer (used for the secret redactor) could probably be reused for this in quite a straightforward way.
Would you be opening a PR? We would be happy to work with you to get it implemented!
Is your feature request related to a problem? Please describe.
A buildkite setup I use has a very long (175 chars) sandboxed path to the build directory, which is printed ~1800 times throughout the build and tests. It makes it hard to quickly parse logs because of wrapping, and that the key relevant detail is a small fraction of the text output.
The paths from within this path are printed from various tools and code paths, and would thus be difficult to tokenize the path at the point of print.
Describe the solution you'd like
A way to replace strings in the log that is displayed in buildkite
Perhaps raw logs could maintain the original strings?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: