Deployment log
Open a deployment's page to follow it live, find the command that failed and copy its output.
On this page
Before you start
- You can open the site in Managed Websites. Anyone who can open a site can read its deployment logs.
- The site has at least one deployment: see Deploy, stop, retry and roll back.
Find out why a deployment failed
Open the deployment
Go to Managed Websites, choose the site, then Deployments under Code & backups, and choose View log on the deployment's row. The banner at the top says where it stopped, such as Build failed on Production.
Read the failing command
Choose Go to failed task. The Job log opens the command that failed, with its Exit code and its last lines of output.
Copy or search the output
Choose Copy output to copy a task's output, or enter text in Search log output to find a line.
Raise a ticket opens a new support ticket with the deployment filled in. To build the same commit again, retry the deployment: see Deploy, stop, retry and roll back.
Read the log
The Job log groups a deployment's tasks in the order they run. Each group reads passed, failed, running or queued.
| Group | What happens |
|---|---|
| Prepare and source | The repository is checked out and your build commands run. |
| Release | The release is uploaded and its shared files are linked. |
| Database | Scheduled tasks and the queue are paused and your database commands run. |
| Switch and after deploy | The site switches to the new release, then your after-deploy commands run. |
The cards beside the log show the deployment's status and duration, its Timing, its Target environment, its Source repository and branch, and its Commit. A variable that is Hidden is masked in the log and in the stored output.
Follow a running deployment
Follow the log
Open the Running deployment and choose Follow log.
The log scrolls with the output as each task runs.