Use > Application deployment > Manage Application Deployments jobs > Work with jobs

Work with jobs

You can use the Jobs window to do any of the following things:

You can also use the Application Deployment Debugger to troubleshoot a job. See Debug a deployment job for more information.

For information about drilling down to detailed information from the Jobs screen, see Jobs screen .

Locating specific jobs

You can use the Search tool to filter the jobs displayed in the Job Logs panel or to locate a specific job (if you know the Job ID).

Jobs Screen Search tool

In this example, only those Deployment jobs that had failed during the Last Week would be listed.

To filter the Job logs:

  1. Go to the Jobs screen (click Jobs in the lower left corner).
  2. Do one or more of the following:
    • Specify the time window
    • Specify the job status
    • Specify the job type
    • Specify a Job ID
  3. Click Search.

When searching by Job ID, you must specify the entire Job ID (no partial IDs or wildcard characters). You can specify multiple Job IDs separated with commas.

To broaden the search and display more jobs, select the “Any” choice in one or more of the drop-down lists.

Pausing a job

You can pause any job that you have deployed that is currently in progress. The Application Deployment administrator can pause any job that is currently in progress.

When you pause a job, Application Deployment will complete the step that it is currently processing and then pause. Until the current step finishes, the status of the job will be “Paused (pending).” After the current step finishes, the status of the job will be “Paused” until it is either cancelled or instructed to resume.

To pause a job:

  1. Go to the Jobs screen (click Jobs in the lower left corner).
  2. Locate and select the job that you want to pause in the Job Logs (see Locating specific jobs).
  3. On the tool bar, click Pause.
  4. Click Yes to confirm.

The job will remain paused until you (or the Application Deployment administrator) resume the job (see Resuming a paused job).

Resuming a paused job

You can resume any job that you have paused. The Application Deployment administrator can resume any paused job.

When you resume a job, Application Deployment starts running the next scheduled step in the job.

To resume a paused job:

  1. Go to the Jobs screen (click Jobs in the lower left corner).
  2. Locate and select the paused job that you want to resume in the Job Logs (see Locating specific jobs).
  3. On the tool bar, click Resume.

The job will continue running from the point at which it was previously paused (see Pausing a job).

Canceling a job

You can cancel any job that you have deployed that is currently either in progress or paused. The Application Deployment administrator can cancel any job that is in progress or paused.

When you cancel a job, Application Deployment will complete the step that it is currently processing and then stop. Until the current step finishes, the status of the job will be “Cancelled (pending).” After the current step finishes, the status of the job will be “Cancelled.” Any remaining steps are left in the “Scheduled” state.

If the job that you are cancelling is a Deployment job, Application Deployment will attempt to roll back the deployment.

To cancel a job:

  1. Go to the Jobs screen (click Jobs in the lower left corner).
  2. Locate and select the job that you want to cancel in the Job Logs (see Locating specific jobs).
  3. On the tool bar, click Cancel.
  4. Click Yes to confirm.

A cancelled job cannot be resumed. If you later decide to deploy this version to the same target, you can simply deploy the same version again.

Rescheduling a job

You can reschedule a “Scheduled” job that you have deployed. The Application Deployment administrator can reschedule any “Scheduled” job.

To reschedule a job:

  1. Go to the Jobs screen (click Jobs in the lower left corner).
  2. Locate and select the job that you want to reschedule in the Job Logs (see Locating specific jobs). It must be in the “Scheduled” state.
  3. On the tool bar, click Reschedule.
  4. Choose a new Stage time, a new Cut Over time, or both.
  5. Click OK.

Note the following:

If a job has been scheduled but is not yet running, and the job has “auto-undeploy” enabled, you will get an information when you reschedule the job indicating that you will need to reschedule both the Undeployment and Deployment jobs.

If Staging has happened, but Cut Over has not yet happened, you can reschedule only the Cut Over segment.

The Reschedule button is disabled when the job is running.

Rolling back a deployment

After a Deployment job that you have deployed has completed, you can manually roll it back. This returns the server to the state it was in prior to the deployment. The Application Deployment administrator can roll back any Deployment job.

See Roll back a deployment for instructions.

If a job fails or is cancelled, and rollback is enabled, Application Deployment will roll it back automatically.

The standard Rollback scripts maintain only one backup version for each release—they remove any existing backup files in order to conserve disk space on the target server. This means that if you roll back a version that is older than the most recently deployed version, Application Deployment will not be able to restore the code files. If you attempt to roll back a previous version, a warning message is displayed, and you can either confirm or cancel the rollback.

Undeploying a deployment

After a Deployment job that you have deployed has completed, you can manually undeploy it. This removes any trace of the deployment, but it does not attempt to return the server to the state it was in prior to the deployment. If no intervening versions have been deployed, the undeploy is equivalent to a rollback. The Application Deployment administrator can undeploy any Deployment job.

An undeploy is a more aggressive type of “undo” operation than a rollback.

Send Help Center feedback