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
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...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG