tomcat undeploy fails if application is not deployed already

I am trialling bamboo, have installed the example application and have tried deploying the angry nerdz application to a tomcat instance.

I figure I need 2 tasks, the first to undeploy angry nerdz , the second to deploy, because deploy by itself fails if angry nerdz is already deployed.

This is all good except however undeploy fails if angry nerdz isn't deployed, which is as expected, but then the build stops.

Is there anyway to circumvent this?

3 answers

Same issue... could you fix it?

I upvote this because I am starting to get more and more annoyed by this behaviour. One workaround could be making the "deploy" task a final task (it will be executed not matter the build result), but indeed Bamboo should allow a single task to be "optional", e.g. if fails does not affect entire build

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,139 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you