mcloud-deployments

Cloud CLI: Deployments Commands

Execute mcloud deployments commands to inspect deployments and their build logs.

Constraints

• Always pass --json when parsing output — plaintext format may change.
• Always confirm context (mcloud whoami --json) before running commands if org/project are not already known.
• Use --deployment IDs in the format depl_* or build IDs; build IDs resolve to their latest deployment automatically.

Commands

deployments list

List recent deployments for a project (default: 20 most recent across all environments).

mcloud deployments list --organization <org-id> --project <project-id-or-handle> --json

Options:

• -o/--organization <id> — Organization ID (falls back to active context)
• -p/--project <id-or-handle> — Project ID or handle (falls back to active context)
• -e/--environment <handle> — Filter by environment handle
• --environment-type <production|long-lived|preview> — Filter by environment type
• --commit <sha> — Filter by Git commit SHA (full or prefix)
• --limit <1-200> — Max results (default: 20)
• --offset <number> — Pagination offset (default: 0)
• --json — Output as JSON

deployments get

Retrieve a single deployment's details by ID.

mcloud deployments get <deployment-id> --organization <

Arguments:

• deployment — Deployment ID (required)

Options:

• -o/--organization <id>, -p/--project <id-or-handle>, --json

deployments build-logs

Fetch build logs for a deployment. Use this to debug build-failed status.

Arguments:

• deployment — Deployment ID (required)

Options:

• -o/--organization <id>, -p/--project <id-or-handle>
• --type <backend|storefront> — Which build log stream to read (default: backend)
• --json — Output as JSON

Deployment Statuses

Examples