Executing Failure Tasks

If deployment or testing fails in an environment or environment group, pre-defined failure tasks can be executed in those environments to configure them as needed. For example, you may want the environments to be re-initialized to their original state.

Prerequisites: If you want to enforce the failure path in the workflow for child release packages or packages linked to deployable release trains, ensure that you set the Execute Child Failure Tasks option in the parent release packages or deployable release trains before linking packages to them. See Adding Failure Tasks.

To execute failure tasks:

  1. When a failure is detected in your deployment process, click the button for the failure transition, such as Fail Deployment or Fail Testing, to initiate any failure tasks.
    • If there are failure tasks, the failure path is followed in the workflow and you are prompted to deploy the failure tasks.
    • If there are no failure tasks and the Require Failure Tasks option is set to No, the release package or deployable release train goes back to the construction state in the workflow.
    • If there are no failure tasks and the Require Failure Tasks option is set to Yes, the failure path is followed in the workflow and you are prompted to create failure tasks before beginning the failure task deployment.
    • If there are child packages or a deployable release train has linked release packages, the Execute Child Failure Tasks option in the parent or train controls whether the child or linked package follows the failure path in the workflow.
    • If the failure deployment fails, you can edit the failure tasks using Restart Failure Tasks.
  2. Navigate to Deployment Tasks > Task Executions and refresh as needed to see the current status.

Related Topics

Starting Deployment

Adding Failure Tasks

Checking Deployment Status

Executing Manual Tasks