Skip to main content
POST
Analyse the latest build of an application

Authorizations

Authorization
string
header
required

JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '

Path Parameters

applicationId
string<uuid>
required

Application ID

Body

application/json
execution_id
string
required

Execution id of the build to analyse. It must be the latest build of the service, latest_build_execution_id in BuildAnalysisState.

Example:

"6e5c1d3a-6b6f-4c35-9a2f-8f1d2c3b4a5e-42"

Response

Build analysis started

service_id
string<uuid>
required
execution_id
string
required

Execution id of the analysed build.

Example:

"6e5c1d3a-6b6f-4c35-9a2f-8f1d2c3b4a5e-42"

status
enum<string>
required

PENDING is queued, COLLECTING reads the build logs and the cache history, ANALYSING waits for the model, then DONE or FAILED. The Dockerfile is resolved before the start answers 202.

Available options:
PENDING,
COLLECTING,
ANALYSING,
DONE,
FAILED
stale
boolean
required

True when the latest build of the service is not the analysed one. The analysis stays readable, but only the latest build can be analysed.

dockerfile_source
enum<string>
required

Where the analysed Dockerfile came from. GIT is the repository at the build commit, INLINE the Dockerfile stored on the job.

Available options:
GIT,
INLINE
failure_code
enum<string> | null
required

Why the analysis failed, when status is FAILED.

Available options:
MODEL_ERROR,
TIMEOUT,
INTERNAL_ERROR
failure_reason
string | null
required

Human-readable detail of the failure, when status is FAILED.

result
object | null
required

Set when status is DONE.

created_at
string<date-time>
required
updated_at
string<date-time>
required