Choose a more unique log-group pattern

petemounce · July 10, 2020, 5:09pm

The --- and +++ patterns to manage log groups are quite common prefixes for build output

FastBuild emits ---------------------------------------------------- before/after stages (fastbuild.org)
diff emits --- and +++ - we use this to prove that generated code that we need to nonetheless source control is up to date

It’s not rare.

Would it be possible to get these patterns (https://buildkite.com/docs/pipelines/managing-log-output#main) changed so that something more unique and uncolliding is the One True Way to divide up logs?

e.g. bk--- etc would do it just fine, I think.

Rose · July 14, 2020, 1:06am

Thanks @petemounce! Yeah, there’s a number of tools (you can add Golang to the list) where the output collides with what we’ve chosen as the Buildkite grouping output. We’ll continue to look at some alternative ideas there… your bk--- suggestion is good!

simonbyrne · August 3, 2020, 3:47am

FYI Travis CI uses a longer string with ANSI escape codes, and lets you mark the begin and end (which allows for nested groups):

github.com

travis-ci/travis-rubies/blob/918fdab9719cbfa8b3cdc65234080e7608722d63/build.sh#L41-L47


fold_start() {
  echo -e "travis_fold:start:$1\033[33;1m$2\033[0m"
}

fold_end() {
  echo -e "\ntravis_fold:end:$1\r"
}