Setting action on failure

Using the BLPackage editor, you can use object attributes to specify how a Deploy Job reacts to a failure when installing a software package or executing an external command.

The options for a software package or external command are:

• Abort — A failure starts a rollback if a rollback is defined for this job. The command generates a non-zero exit code. Deploy Job results show the job as failing.
• Ignore — A failure is ignored and the job continues. Deploy Job results show the job as succeeding. By ignoring the failure and letting the job continue, you can fix any problems that caused the failure, comment out any successful elements in the BLPackage (see Commenting-out-assets), and run the Deploy Job again.
   For example, suppose you are installing five RPMs named A, B, C, D, and E. Installation of A and B have no effect on the operation of C, D, and E. If another RPM is required to install A and B, their installation will fail. However, if you set ActionOnFailure to Ignore the A and B RPMs, you could let the Deploy Job continue so the C, D, and E RPMs install successfully. Later, you could install the missing RPM, use the BLPackage editor to comment out the C, D, and E RPMs that already installed successfully, and run the job again.
• Continue — The failure is ignored and the job continues. Deploy Job results show the job as failing.

The Continue action takes precedence over the Ignore action. If a Deploy Job includes multiple commands that have failed and the ActionOnFailure for these commands is defined as both Ignore and Continue, the overall job appears to have failed.

To set action on failure

1. Right-click in the hierarchy view and select a software package or external command.
2. Enter a value for ActionOnFailure by clicking in the Value column and selecting an option from the drop-down menu.