Skip previously successful tasks when (Re)running failed deployment/release

paul strachan

Hi,

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)

Cheers,

Paul

Marcin Oles

Hi,

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:

• stage 1 (automatic): build plan stage 1
• stage 2 (automatic): build plan stage 2 if needed
• ...
• stage N (automatic): build plan stage N if needed
• stage N+1 (manual): deployment tasks #1-#4, not rerunable
• stage N+2 (automatic): deployment task #5, rerunable
• ...

Of course this attempt might require some modifications and in your case might not be possible. Just a suggestion.