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 you trigger a new action while one is already running depends on the action:
- Deploys are queued. Both a manual deploy and a push-triggered auto-deploy are held and run automatically once the current operation finishes. Triggering a deploy manually during an active operation shows a confirmation, then a "Deployment queued" message. (A push to a stopped environment is the one exception — it is ignored rather than queued.)
- Rollback and Stop take over immediately. These cancel the operation in progress and run right away — a rollback shouldn't have to wait behind a broken build, and a stop should bring the environment down now. You'll be asked to confirm, since the running operation is cancelled.
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