Log shows build failed but Bamboo said Build Sucessful

[Mary Hsieh]

I'm new to Bamboo and I'm using a windows command line script to do my build. I can clearly see the in the log that the build failed.

error 05-Dec-2012 15:08:08 ecomarm: fatal: No license available for "source_analysis"
error 05-Dec-2012 15:08:08
error 05-Dec-2012 15:08:10 Error: build failed

However, the Bamboo notification tells me the build is successful. Why is that and how can I fix it?

I'm using Bamboo 4.2.1

[Nick Hilton · Accepted solution]

For others arriving from search engines, one can use

{code}

set -e

{code}

At the top of their script so it errors out on any error.

[Atul Yadav]

What is the actual content on the code, 

{code} -- ?

set -e

{code} -- ?

[Mary Hsieh · Accepted solution]

The script always exits with 0 since the script itself executed normally. What was done originally was all the project builds are combined into one script file. It looks like Bamboo only looks at the last few lines of the script results. So if the script failed in the middle, then it will not catch it. So what had to be done was to split up each project build into its own Bamboo task so Bamboo can detect the failure. A little cumbersome but at least it worked. Maybe the task section in the documentation explained this. Sorry if I missed it.

[Przemek Bruski]

The script has to exit with a non zero status for the build to fail.

[Brian Mackey]

How do you see what the script reports or modify it?