Versions and builds

Immutable app identifier. Unique among the authenticated organization's live apps: it cannot be changed after creation, and it becomes available again once the app it named reaches deleted.

Monotonically increasing per app.

The build that produced this version's image. Both source types build. A code source bakes an image around a submitted codebase, a container source builds the customer's own wrapper Dockerfile. A version created by an update carries the image, and therefore this build, forward.

Preferred GPU type of this version, taken from the config snapshot.

Who created this version: the authenticated user (JWT) or the API key. displayName is the name captured at write time.

Wall-clock milliseconds of the named build (completedAt - createdAt on that build). Null while the build is running or when no completion time is available. Bytes and units are not included. This is a raw millisecond count.

Structured diff against the previous version. Null on version 1.

Number of items in the collection this page was drawn from.

Whether the actor is a user (JWT) or an API key.

True when this version names a different image than the previous one (buildId or imageRef changed). False for a config-only update, which carries the image forward.

Keys added, removed, or changed between consecutive versions. For environment variables, changed is keys whose value changed (the value itself is never returned). For endpoints the key is the path. For volumes it is mountPath. changed is omitted on those two (a path either exists or does not).

Keys added, removed, or changed between consecutive versions. For environment variables, changed is keys whose value changed (the value itself is never returned). For endpoints the key is the path. For volumes it is mountPath. changed is omitted on those two (a path either exists or does not).

Keys added, removed, or changed between consecutive versions. For environment variables, changed is keys whose value changed (the value itself is never returned). For endpoints the key is the path. For volumes it is mountPath. changed is omitted on those two (a path either exists or does not).

Immutable app identifier. Unique among the authenticated organization's live apps: it cannot be changed after creation, and it becomes available again once the app it named reaches deleted.

Where a build's source came from: code for a customer code submission, container for a customer wrapper Dockerfile. repository and revision are not yet recorded (both sources are zip uploads) and will be added when the platform stores that provenance.

Who performed an action: the authenticated user (JWT) or the API key. kind says which, so id (that actor's UUID) is resolvable to the right thing. displayName is its name captured at write time, so it renders as it was even if the user or key is later renamed. Used as Build.triggeredBy and Version.author.

Build/validation lifecycle status.

The version this build produced. A code build's version is created together with the build, so this is populated in every status. It is null only when no version references the build. A code update carries an image, and so its build, forward onto a new version, so a build may be named by several versions. This is the earliest, the one the build actually produced.

Version number of versionId. Null when versionId is null.

Error message or failure reason. Null when the build is still running or succeeded.

Exit code of the build container. 0 only when the build succeeded. On failure, that container's non-zero code. Null when it exited 0 or never ran, and when the builder could no longer read the code. In both of those the failure belongs to another phase, named by phases and logTail. Null while the build is running.

The last lines of the build output that belong to the app's own code: what the model file printed and raised when the build imported it, the build's messages about the codebase and its requirements, and the output of the steps that install the declared requirements or, for a container source, run the Dockerfile. Output of the platform's own build steps is never included, on successful and failed builds alike. A failed build's tail always says why: when none of that output explains the failure, it ends with one line that names the platform step the build stopped in, or says that the build was stopped, most often at its time limit. At most 100 lines and 16 KiB. Null while the build runs.

Wall-clock milliseconds from createdAt to completedAt. Null while the build is still running or when no completion time was recorded.

Observed build phases with their timings, recorded once the build is terminal. Empty until then. Phase lists differ by source.type. Never assume a fixed list.

When the build reached a terminal status (ready/failed/superseded). Null while running or for terminal builds recorded before this was tracked.

Number of builds recorded for this app.

Number of versions recorded for this app. Same value as listVersions summary.total. A config-only update increments this without incrementing total.

The kind of source that produced this build: code or container, straight from the build record. Build phases differ by kind, so clients must not assume a fixed phase list. Not modeled as an enum so adding a kind later does not churn the existing source-type constants this API shares.

Whether the actor is a user (JWT) or an API key.

Phase identifier, e.g. prepare, build, index. Deliberately not an enum. New build kinds report new phases without a contract change.

Null while the phase is still running.