Deployment view
The deployment view is the page you land on when you start a deployment or open one from the deployments list. It answers three questions while the deployment runs: what's being deployed, how far it has got, and what you can still do about it.
Walk through the page below:
The headline
The page opens with a sentence that names what's happening, such as Deploying release 0.0.15 → 0.0.16 to Development Uruguay. The verb follows the lifecycle (Deploying, Waiting for approval to deploy, Rolling back, Deployed), and the version pair shows the release going out and the one it replaces. The short SHA in the build links to the commit in your repository.
The line of stages
The stages run in this order:
Setting up → Before hook → Waiting for instances to be healthy → Switching traffic → Finalize
You won't always see all five. The line reflects what this particular deployment actually does:
- A serverless scope has no instances to wait for, so there's no instances stage.
- An initial deployment, or a scope that doesn't support traffic switching, has no traffic stage.
- The before hook stage appears only when your organization declares a hook for deployments.
A deployment running on a scope you built yourself gets the same treatment. The page reads the structure the deployment reports rather than a list of stage names nullplatform knows in advance, so your own stages and their names show up in the line just like the built-in ones.
Clicking a completed stage
Click any completed stage to send the panel back to it and inspect what happened earlier without waiting for the deployment to end. Stages the deployment hasn't reached yet aren't clickable.
The stage panel
The panel shows one stage at a time: the one the deployment is on, or the one you clicked. When a step fails, its row carries the error message and the evidence the stage collected, such as how many instances never turned healthy and why, which is the detail the stage summary can't give you.
The logs follow the selected stage. When the deployment reports step-level detail, they're narrowed to that stage's window, so you read the lines from the minutes you care about instead of scrolling one long stream.
Finishing, rolling back, and cancelling
The page actions follow the deployment, so you only see the ones that apply. A blue-green deployment parks at 100% traffic and waits, by default for two hours, precisely so the decision can be weighed. All three actions are irreversible, so each one asks for confirmation and spells out what it destroys before it runs.
| Action | What it does | Getting back |
|---|---|---|
| Finish | Retires the previous version's instances and completes the deployment. | Rolling back afterwards requires a new deployment. |
| Fast rollback | Returns all traffic to the previous version and destroys the new instances. | Deploying again requires a new deployment. |
| Cancel deployment | Stops the deployment and destroys anything it created. | Deploying again requires a new deployment. |
If you do nothing, a deployment parked at full traffic finishes on its own when the wait runs out. The Finalize stage shows the time remaining.
Catalog
When your organization defines a deployment metadata specification, the Catalog panel sits under the headline with this deployment's metadata rendered against it. You can edit it in place from the same panel, provided metadata editing is enabled for your organization.
Organizations without a deployment specification don't see the panel at all.
Deployment groups
A deployment group deploys to several scopes at once, and it gets the same page.
The difference is that the stages count the fleet rather than one deployment, so a stage reads 3/5 scopes and tells you how many failed or were cancelled. The page actions apply to every scope in the group at once, and the confirmation says how many deployments it's about to finish, roll back, or cancel.
When a group is waiting on an approval, the gate is the first stage on the group's line, with the checklist as that stage's panel. A guarded scope in the group delegates its checklist up to the group, so one approval holds the whole fleet instead of one per scope. The Catalog panel isn't shown on group pages.
Switching between this view and the previous one
The deployment view reaches your organization as a rollout you can walk back. The control sits beside the page title:
- On the new view it explains what changed and offers a short walkthrough of the page.
- If it doesn't work for you, switching to Previous version puts you back on the older page right away, and asks what went wrong so the team hears about it.
The new-deployment form is a separate rollout, so you can keep this view while putting the form back, or the other way round.
Next steps
- Deployment lifecycle and flow: the statuses behind the stages, and the built-in rollout strategies
- Deployments: deployment groups, approvals, and how deployments fit together
- Deployment strategies: control how traffic shifts and when a deployment rolls back on its own