Timeouts for simulate and staging phases
Deploy Jobs include two properties that let you set timeout values for actions performed during the Simulate and Staging phases of a job. These properties are unique to Deploy Jobs.
By defining timeouts for these properties, a job can be set up so a deployment returns an error or the job fails if the Simulate or Staging phases take too long to complete. Without timeouts, a Deploy Job may wait indefinitely to complete preliminary phases.
To define timeouts, enter values for one or both of the following Deploy Job properties:
DEPLOY_JOB_NSH_CMD_TIMEOUT— Sets a timeout value in seconds for agent commands used to determine file system sizes and capacities during the Simulate and Staging phases of a Deploy Job.
DEPLOY_JOB_URL_COPY_TIMEOUT— Sets a timeout value in seconds for any copying of payload files that occurs during the Staging phase. This option is only applicable if you are deploying a package of patches or software and the package is defined to use the Copy to Agent staging option.
For Deploy Jobs, job-level timeout properties only apply to Software Deploy Jobs, basic BLPackage Deploy Jobs, or advanced BLPackage Deploy Jobs with phases that run sequentially. Because job-level timeouts only apply to jobs that are scheduled, job-level timeouts do not apply to undo jobs, which you cannot schedule.