Deployment lifecycle
Each time you trigger a deploy, Velumi creates a new deployment record for that environment. The deployment moves through a series of statuses as it progresses.
Statuses
| Status | Meaning |
|---|---|
pending | Queued — no work has started yet |
building | Source is being compiled and the image built |
built | Build finished — image ready, waiting for the runner to deploy it |
deploying | Image is being rolled out to the runner |
ready | Live and serving traffic — this is the current deployment |
failed | Build or deploy failed — never served traffic |
superseded | Was previously current, replaced by a newer deployment |
ready, failed, and superseded are terminal — the deployment will not change status after reaching one of these.
What "current" means
Each environment has exactly one current deployment — the one with status ready that is actively serving traffic. When a new deployment reaches ready, the previous current deployment transitions to superseded.
Triggering a deployment
Go to Project → Environment → Deployments and trigger a new deployment. You can also restart a stopped environment or retry a failed deployment from the same view.
A deployment is also triggered automatically after a project is created.
One operation at a time
An environment runs one deployment or lifecycle operation at a time. What happens when a new deploy is triggered during an active one depends on how it was triggered:
- Manual deploys are rejected. While a deployment or other operation is in progress, the manual deploy button is disabled — you can't start a second one by hand.
- Automatic deploys are queued. A push to a branch with auto-deploy enabled is held and deploys automatically once the current operation finishes.
Detail page
Click any deployment in the list to open its detail page. It shows:
- Status and short deployment ID
- Source — branch, commit hash, and a link to GitHub (or "Archive upload" for zip sources)
- Triggered by label, and PR number if applicable
- Build duration
- Build log
- Error message for failed deployments
- A Preview button if the deployment has a preview URL