Running Deploy Jobs
Right-click either an individual Deploy Job or the Batch Deploy Job and select Execute.
Customer environments typically produce more than one Deploy Job. The recommended method is to execute the Batch Deploy Job to update servers.
The Tasks in Progress view shows the executing job.
- In the Folder view, right-click the job name and select Show Results.
A view for the job opens in the content editor (typically in the upper right corner of the console).
- Click the job run.
The right panel shows the job's progress and log messages. A Deploy Job can be in the Simulate, Stage, or Commit state.
A solid green check mark in the Commit column indicates that, although patches are applied successfully, servers are not rebooted.
Optionally, you can right-click the green checkmark in the Commit column to display reboot options for the servers, and select one of the options.
The checkmark in the commit column is green, whereas the checkmarks in other columns are white with green backgrounds.
The following example shows a Patching Job that includes Remediation, with a Batch Deploy Job and several server Deploy Jobs. Notice that the Patching Job Run has two nodes under it.
- Analysis run — This node includes a Server View and an Object View, as described previously.
Remediation run — This node includes the Batch Job, with all of the Deploy Jobs contained in it.
Starting with BMC Server Automation version 8.2, the Deploy Jobs are chained to the parent Patching Job, and the parent Patching Job is marked as complete only after all of the Deploy Jobs finish execution.