My team and I find the default raw logs very impractical. Consider the following example:
simple 15-Dec-2021 20:35:53 Running pre-build action: VCS Version Collector
simple 15-Dec-2021 20:35:53 Starting task 'install' of type 'com.atlassian.bamboo.plugins.bamboo-nodejs-plugin:task.builder.npm'
command 15-Dec-2021 20:35:53 ...
error 15-Dec-2021 20:35:54 npm info it worked if it ends with ok
error 15-Dec-2021 20:35:54 npm verb cli [
error 15-Dec-2021 20:35:54 npm verb cli '/appl/nodejs/node-v14.15.1-linux-x64/bin/node',
error 15-Dec-2021 20:35:54 npm verb cli '/appl/nodejs/node-v14.15.1-linux-x64/bin/npm',
error 15-Dec-2021 20:35:54 npm verb cli 'ci',
error 15-Dec-2021 20:35:54 npm verb cli '--verbose',
error 15-Dec-2021 20:35:54 npm verb cli '--ignore-scripts'
error 15-Dec-2021 20:35:54 npm verb cli ]
error 15-Dec-2021 20:35:54 npm info using npm@6.14.8
error 15-Dec-2021 20:35:54 npm info using node@v14.15.1
error 15-Dec-2021 20:35:54 npm verb npm-session 550eb15955fb836f
error 15-Dec-2021 20:35:54 npm info prepare initializing installer
error 15-Dec-2021 20:35:54 npm verb prepare starting workers
error 15-Dec-2021 20:35:54 npm verb prepare using package-lock.json
error 15-Dec-2021 20:35:54 npm verb checkLock verifying package-lock data
The error prefix can go on for hundreds of lines, which makes it really hard to find an actual "error" string within the logs.
Is there any way to get rid of those line prefixes? And maybe even the datetime string (which is also not always useful)?
