# Deployments and rollback

Source : https://webgune.cloud/en-us/docs/deploiements-rollback · Mis à jour le 2026-10-27

# Deployments and rollback

A service's **Deployments** tab is its full history: every build is listed there with its commit, status, duration, and logs.

## Deployment lifecycle

| Status | Meaning |
|--------|---------------|
| **In progress** | The build is running, live logs |
| **Success** | Image built and deployed |
| **Failed** | The build or a check failed. Nothing was deployed |
| **Canceled** | Build manually interrupted |

A successful deployment replaces the previous one **with no downtime**: the new version starts, and traffic only switches over once it's ready.

## Rolling back

Every successful deployment keeps its image in the internal registry. To go back to a previous version:

1. Open the service's **Deployments** tab.
2. Find the target deployment in the history.
3. Click **Rollback**. The image from that time is redeployed as-is, with no rebuild.

The rollback is nearly instant since no build is needed. The current environment variables apply (they are not restored to their state at that time).

## Canceling a build in progress

A build started by mistake (or stuck) can be canceled from the deployment row, **Cancel** button. The service keeps running on its previous version.

## Build logs

Each build's logs are **persisted**: you can reopen a deployment from weeks ago and read its full output. Essential for comparing a passing build with one that breaks.

> **Automatic deployment**: if the service follows a GitHub branch, every push triggers a build ([continuous deployment](/docs/cicd-introduction)). [kx712.yml checks](/docs/kx712-yml) let you block the deployment if your tests fail.