Read the build log of a publish
get_publish_logs
Reads the build output of a publish, which is where the reason for a failed publish actually lives.
Scopelogs:readRead only
get_publish_status only says that a publish failed, and this says why. Leave out deploymentId for the most recent publish, or name one from list_deployments. A failed publish carries its error alongside the lines.
At most 200 lines come back per call, with total and hasMore, so page with offset. Only the last 1,000 lines of any build are kept at all. See When a publish fails.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
projectId |
string | Yes | The site id. |
deploymentId |
string | No | A specific publish, from list_deployments. Leave it out for the most recent one. |
offset |
integer | No | How many lines to skip. The oldest kept line is 0, which is also the default. |
limit |
integer | No | How many lines to return, up to 200. Defaults to 200. |