Using Bamboo 5.9.2 with Subversion. Our deployment process runs a set of predefined tasks, some of these tasks cannot be rerun and any of the tasks could fail.
If task #5 fails, currently we need to edit the deployment plan and manually disable tasks 1-4 before rerunning and then remember to re-enable the tasks once deployment completes successfully.
Is it possible to configure Bamboo deployment process to automatically 'skip' tasks that were previously completed successfully when re-running a deployment/release (i.e. start with the first failed task)
I could imagine each task would contain an option to preserve its state, and when deploying an option would be to ignore already completed tasks (if task is configured for that)
the scenario you've described can't be currently achieved using deployment projects in Bamboo.
However, what can work for you as a workaround (note: not a recommended way to run deployments) is to move deployment phase to the build plan as additional, manually triggered stages. There are drawbacks of doing so, but it will allow you to perform action "rerun only failed jobs", which will rerun only from the stage that has failed.
So you can have multiple stages. As an example:
Of course this attempt might require some modifications and in your case might not be possible. Just a suggestion.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot