Deployments
Shiprr keeps deployment history for each app so you can review release attempts, inspect status, and roll back when a release goes wrong.
Deployment history#
Open your app in the dashboard and review the deployment list to see recent deploy attempts, build linkage, commit metadata, and final status.
Deployment status#
A deployment can move through queued, building, deploying, succeeded, failed, or canceled states depending on where the release is in the build and runtime rollout flow. Use the status together with logs to decide whether the failure came from source build, image creation, startup, health checks, or runtime configuration.
Rollback#
If a previously completed build is known good, you can redeploy it from the deployment/build history. Rollback reuses that build's existing image, skips source rebuild, and creates a fresh deployment attempt.
The rollback deployment uses the app's current runtime settings, including replicas, resources, environment variables, health checks, domains, and routing rules. It does not restore database contents, external services, or the older deployment's full configuration snapshot.
What to check first#
- Build failed — Open the build log and review the last failing step.
- Deploy failed after build — Review runtime status, health checks, and runtime logs.
- App is live but unhealthy — Check health check path, start command, env vars, and resource limits.