Debug a deployment job

You can use the Application Deployment debugger to troubleshoot a Deployment job, a Rollback job, or an Undeploy job (you cannot use it to debug a Make Version job).

Consider the following scenario:

1. A Deployment job fails because of a problem in a specific component.
2. You make a change to fix that component.
3. You then create a debuggable job and launch the debugger.
4. In the debugger, you disable as much of that job as possible—this enables you to quickly test your change and see if it works.
5. If your change works, you can then enable more of the job until you are confident that the entire job works.

Depending on your troubleshooting objective, you can launch the debugger from either the Deployment screen or the Jobs screen. You can use the debugger to do the following things:

• Use breakpoints
• Deploy or skip any component
• Deploy to or skip any server
• Single-step through a deployment
• Enable or disable tier provisioning and backup steps

When you skip a component or server, all job steps pertaining to that component or server—including rollback and undeployment steps—are skipped.

To run the debugger, you must either have Edit permission for the pertinent application (see Set permissions) or Manage Application Deployment permission (see Set permissions).