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?
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
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events