tomcat undeploy fails if application is not deployed already

[Stephen Newman]

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?

[Michael Benz]

We typically just copy the application directly into the webapps folder to deploy and delete the file to undeploy. But since I started using the Deploy Task more I thought also the Undeploy would come in handy ... just before I saw this ;-)

[Sebastian Davids]

https://jira.atlassian.com/browse/BAM-13407

[Antonio Anzivino]

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

[Séb P.]

Same issue... could you fix it?