NuPaaS DocsPromote & roll back
Three different things get called "promote" or "roll back" on a platform. NuPaaS keeps them separate: rolling back a deployment, promoting or rolling back a canary, and promoting one environment onto another.
Rolling back a deployment
A rollback does not rewind history. It creates a new deployment from a previous deployment's image and rolls that out, so the deployment list keeps a complete forward record of what happened.
Open a deployment at /orgs/<org>/projects/<project>/deployments/<seq> and press Rollback. You are asked to confirm, and on success you land on the new deployment's detail page.
platform deploy rollback --deployment <deploymentId>When the rollback button appears
The control is shown only when a rollback can actually succeed. Two conditions must both hold:
| Parameter | Type | Description |
|---|---|---|
| Deployment status | active | failed | rolled_back | A build that is still queued, building or deploying cannot be rolled back — cancel it instead. |
| Image digest | present | There must be a built image to roll back to. A deployment that failed before producing an image has nothing to redeploy. |
Cancelling a build in flight
While a deployment is building or deploying, the deployment page offers Cancel rather than Rollback. A deployment stuck in queued or pending for more than five minutes is flagged as stuck and offered a retry.
Canary deploys
A canary deploy runs a new version alongside the stable one and sends it a fraction of traffic. The initial weight defaults to 10 percent and may be set between 1 and 50; afterwards it can be adjusted to any value from 1 to 99.
Managing a running canary
When a deployment is in the canary status, its detail page shows a canary panel with three actions:
- Adjust weight — change the share of traffic going to the canary.
- Promote — make the canary the stable version.
- Roll back — discard the canary and keep the current stable version.
Promoting an environment
Environment promotion is a different operation from anything above. It takes a source environment and a target environment and promotes the source's state onto the target — the usual staging-to-production move. It operates on environment ids, not deployment ids.
Promotion is available from the environments page at /orgs/<org>/projects/<project>/environments. See Environments and secrets for how environments are structured.