Managing deployments
Inspect, cancel, and spin down Easel deployments.
The deployment history for a project shows every deployment created from Git, the CLI, or the dashboard.
Deployment details
A deployment detail page includes:
- Status
- Environment (Preview or Production)
- Source branch and commit
- Commit author and message
- Creation time and build duration
- Framework and build configuration
- Generated resources
- Deployment URLs (commit, branch, pull request, and production when applicable)
- Build and runtime logs
Use these details to determine exactly what source and configuration produced the deployment.
Deployment statuses
| Status | Meaning |
|---|---|
| Queued | Waiting for build capacity |
| Provisioning | Preparing the build environment |
| Building | Installing dependencies and producing build output |
| Assigning domains | Publishing output and assigning URLs |
| Ready | Published and able to receive traffic |
| Failed | Build or publication did not complete |
| Canceled | Stopped before becoming ready |
| Skipped | Not built because changes did not affect the project |
| Spun down | Taken offline after Ready or Failed |
Production deployments that are Ready but not Current appear as Staged when auto-assign is off. Current marks the Production deployment serving production domains.
Cancel a deployment
You can cancel a deployment while it is Queued, Provisioning, Building, or Assigning domains.
Canceling:
- Stops remaining build work
- Prevents the deployment from becoming Ready
- Leaves existing stable URLs unchanged
- Preserves logs generated before cancellation
Any workspace member can cancel. A deployment that has already reached Ready cannot be canceled; spin it down instead if you need to take it offline.
Spin down a deployment
Spin down takes a Ready or Failed deployment offline. The unique deployment URL stops serving because only Ready deployments are served.
Easel blocks or warns when the deployment is required for active production routing. Prefer Instant Rollback or promote another deployment before spinning down Current production.
There is no separate delete-deployment action today. Spin down is the way to retire a deployment's serving surface.
Creating a new deployment from the same source
There is no one-click "redeploy this deployment ID with historical settings" action.
To ship the same commit again with current configuration:
- Push the commit again, or run
easel deployfrom that revision - Use dashboard Deploy for the production branch HEAD
- Promote a Preview deployment to production (rebuilds that commit with current Production environment variables and the source deployment's project settings snapshot)
New deployments snapshot environment variables and project settings at creation time. They do not mutate the original deployment.
Filter deployment history
In the dashboard, use the deployments list to distinguish:
- Latest deployment for a branch
- Latest Ready deployment for a branch or pull request
- Current production deployment
- Staged Production deployments waiting for promote
- Previous production deployments eligible for Instant Rollback
Retention
Easel does not enforce plan-based deployment or log retention limits in product today.
Deployments remain in history until you spin them down or the project/workspace lifecycle removes access. Unique URLs resolve only while the deployment is Ready.