App Deployment History and Rollback

Who this is for

Users who want to review past deployments for an app, understand what changed, or roll back to a previous working version.


How to View Deployment History

  1. Open the app detail.
  2. Click the Deployments tab.
  3. The last 50 deployments are shown in reverse chronological order.

Each deployment entry shows:

  • Date and time of the deployment
  • Image ref or tag (the Docker image used)
  • Commit SHA (for git-source apps)
  • Status (succeeded / failed / rolled_back)

Expanding a row reveals the step-by-step build log and the Roll back to this version button for prior succeeded deployments.


How to Roll Back a Container App

For apps deployed from a Docker image (source: docker):

  1. In the Deployments tab, expand the deployment you want to roll back to.
  2. Click Roll back to this version (only available for prior succeeded deployments with a saved image reference).

CloudAIPilot re-pulls and runs the image from that deployment.

Note: Compose apps do not support rollback by image tag. Roll back compose apps by redeploying from a previous git commit or reverting your docker-compose.yml in git.


How to Roll Back a Git-Source App

For apps built from git (source: git):

  1. In the Deployments tab, expand the deployment you want to roll back to.
  2. Click Roll back to this version — CloudAIPilot redeploys from the saved image tag for that commit.
  3. Alternatively, use the Commit Picker in the Overview tab to deploy any specific commit SHA.

Re-running a Failed Deployment

If a deployment failed partway through:

  1. Find it in the Deployments tab.
  2. Click Retry to re-trigger the same configuration.

What Success Looks Like

The rollback deploy completes. The app's commitSha or imageRef updates to the rolled-back version. The Activity Center shows the deploy as completed.


Common Issues and Fixes

IssueLikely causeFix
Rollback button missingCompose app (not supported)For compose: revert in git and redeploy, or update compose YAML.
Rollback fails — "image not found"Old image was removed from registryRe-tag and push the old image, then retry.
Git rollback fails — commit not foundCommit was garbage-collected from the remoteUse a tag instead of a raw SHA.

Related Articles