Deploy Job - General
The General panel lets you provide information that identifies a Deploy Job.
Optional descriptive text.
Folder in which to store the object.
Number of targets to process in parallel
Choose one of the following options:
Set execution override
Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.
Clear execution override
Remove an existing execution override.
If you are running an advanced Deploy Job and you are executing Phases of a Deploy Job separately, the job uses the most recent override settings when each phase executes. For example, consider this scenario:
- UserA creates a Deploy Job with an execution override. In other words, the job should always run as UserA.
- UserB runs the Commit phase of the job using the job's override settings (that is, the job executes as UserA).
- UserA clears the execution override.
- UserB attempts to run an undo of the job. The job fails because there is no override set. The job attempted to run as UserB.
If the phases of a Deploy Job are run consecutively, changing override settings are not a problem. Thus, the issue is not a concern when you run:
- Basic Deploy Jobs. You cannot schedule phases separately for Basic Deploy Jobs.
- Advanced Deploy Jobs, if you have selected the Execute selected phases sequentially option (see Phase scheduling and execution for information about that option).
Where to go from here
Deploy Job - Package (for a BLPackage Deploy Job)
Deploy Job - Software (for a Software Deploy Job)