build_logs
Creates, updates, deletes, gets or lists a build_logs resource.
Overview
| Name | build_logs |
| Type | Resource |
| Id | deno.deployment.build_logs |
Fields
The following fields are returned by SELECT queries:
- get_build_logs
| Name | Datatype | Description |
|---|---|---|
level | string | (example: info) |
message | string | (example: Downloaded https://deno.land/std@0.202.0/testing/asserts.ts (2/3)) |
Methods
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
get_build_logs | select | deploymentId | This API returns build logs of the specified deployment. It's useful to watch the build progress, figure out what went wrong in case of a build failure, and so on. The response format can be controlled by the Accept header; ifapplication/x-ndjson is specified, the response will be a stream ofnewline-delimited JSON objects. Otherwise it will be a JSON array of objects. |
Parameters
Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
| Name | Datatype | Description |
|---|---|---|
deploymentId | string | Deployment ID |
SELECT examples
- get_build_logs
This API returns build logs of the specified deployment. It's useful to watch
the build progress, figure out what went wrong in case of a build failure,
and so on.
The response format can be controlled by the Accept header; ifapplication/x-ndjson is specified, the response will be a stream of
newline-delimited JSON objects. Otherwise it will be a JSON array of
objects.
SELECT
level,
message
FROM deno.deployment.build_logs
WHERE deploymentId = '{{ deploymentId }}' -- required
;