Bamboo log line categories (build, command, error, simple)

Sebastien Ashby December 20, 2022

Question about the internals of how Bamboo generates the first work in each line.
These appear to be categories.
I've seen:

  • build
  • command
  • error
  • simple

What conditions does Bamboo use to determine what the label/category is prefixes to each line of the logs?

1 answer

1 vote
Eduardo Alvarenga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 20, 2022

Hello @Sebastien Ashby

Welcome to Atlassian Community!

Bamboo uses different classes to define log strategies:

  • SimpleLogEntry - Generic messages, used for informative purposes. May also be used by certain tasks such as the VCS Checkout task
  • BuildOutputLogEntry - Build output, standard output (File descriptor 1)
  • CommandLogEntry - Tasks that are run on the Agent such as replacing variables, running external processes that would call Tasks, etc
  • ErrorLogEntry - Build errors or any output not redirected to File descriptor 1 (stdout)

Sincerely,

 

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

Sebastien Ashby December 21, 2022

Hi @Eduardo Alvarenga

What conditions need to be met for a line to be considered a "Build errors"?

This aside from ouput not directed to STDOUT(file descriptor 1).
I can assume that STDERR(file descriptor 2) is one of them.
Another might be an exit code/status.
Anything else which directs a log entry to "ErrorLogEntry"?

Like Nico Schuurmans likes this
Nico Schuurmans March 27, 2024

I get the impression that Bamboo is prefixing "error" for everything that returns a non zero exit code, which is often confusing, especially when one command results in many output lines.

For example if you use a Bamboo dockerized job and the image cannot be found locally, you get an "unable to find image locally" and each pulled layer is prefixed with "error"

If you use a tool that gives a warning "using version x.y.z but version a.b.c is available" the same thing. I was hoping to get a bit more control about what Bamboo is prefixing as error, and now it seems a bit "black and white" making almost everything an error.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events