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

Detecting errors during build and deployment scripts


I'm working on a client's build server (a on prem Bamboo install) and the person who originally set it up never got the build and deployment scripts to detect errors from MSBuild or when deploying over the network.


This often leads to us deploying incomplete projects as a microservice may have failed to build, or sometimes our IIS reset doesn't clear file locks or we lose permissions to overwrite our Citrix applications.    If you are watching the logs as they fly by, the errors are highlighted in red, but the scripts don't fail and Bamboo says either the build or the deploy was successful.

I am not that familiar with Bamboo myself.  Does anyone have any good resources or tips for this particular issue and how I could go about resolving it?




1 answer

0 votes
Bloompeak Support
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Jun 25, 2020

Hi @dguisinger ,

If it is linux bash script you should set 'set -e' parameter, so that the script will exit on error.

set -e# Any subsequent(*) commands which fail will cause the shell script to exit immediately

If it is Window PowerShell script, you should set $ErrorActionPreference = "Stop" parameter.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events