Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How do you capture a task error during a build?

If a task that is executed as part of a build gets an error, like trying to delete a directory that doesn't exist, how do you capture that error so the build will also fail? Currently, any inline script commands that execute as part of task do not cause the build to fail even when the command gets an error. I am guessing that the script is currently returning a "zero" return code as long as it executes despite whether or not it fails. If this is the case, I could use an example of how to return a "non-zero" return code from an inline script task. Is there any documentation available about handling errors in build job tasks?

1 answer

1 accepted

2 votes
Answer accepted

Hi @tclements

The script is returning the same error code that a bash script would return (I'm assuming you are using a Linux script). By default, a script will only return the error code of the last line run. In bash for example if you want to change this behavior you need to add the following line at the beginning of your script:

set -e

A different user was facing a similar issue in this question:

Please let me know if that fixes the issue.

Hi @Daniel Santos ,

Thanks for the response. I am using a script task but using "cmd.exe" as the interpreter. I didn't realize that the script will only return the error code of the last line run so that helps. I was able to get it working by exiting the script with the built in %ERRORLEVEL% parameter.

echo "Exiting with return code: " %ERRORLEVEL%

It would be handy to have the script stop after any failed commands. Instead of having to check "%ERRORLEVEL%" before every command, is there a "cmd.exe" setting similar to your bash "set -e" example that would stop the script on a failed command?

Hi @tclements

I'm not an expert on Windows scripting, but I was able to find an article that will probably help you. 

It does say that windows don't have an option similar to set -e.

I hope that helps.

Like tclements likes this

Hi @Daniel Santos 

That helps. We will check the %ERRORLEVEL% parameter after each command and exit with that parameter so that any windows script failed commands will return the appropriate exit code to stop the bamboo build and/or deploy.

Awesome! I'm glad that helped =]

Jimmy Seddon Community Leader Dec 06, 2019

Hi @tclements,

Just going to offer this as another suggestion (we are also a Microsoft shop) we converted a number of our scripts to PowerShell which made capturing/surfacing errors to the root of the script execution much easier.

Not sure if that is an option for you, but thought I'd suggest it as it made our lives easier.


Like # people like this

That is a great suggestion too.
Than you very much for adding that here @Jimmy Seddon! =]

Like # people like this

Hi @Jimmy Seddon ,

Yes, we have a mixture of windows scripts and PowerShell scripts and are starting to find the benefits of using PowerShell as well.

Thank you for the suggestion!

Like Daniel Santos likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events