Managing deployments
Inspect, cancel, and spin down Easel deployments.
A project's deployment history lists every deployment created from Git, the CLI, or the dashboard. Deployments stay in history until you spin them down.
Deployment details
A deployment's page shows its status, environment, source branch and commit, author and commit message, creation time and build duration, framework and build settings, generated resources, URLs, and build and runtime logs. Use it to see exactly what source and configuration produced the deployment.
Deployment statuses
| Status | Meaning |
|---|---|
| Queued | Waiting for a build slot. See Build queue |
| 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 | The build or publication didn't complete |
| Canceled | Stopped before becoming Ready, including by an Ignored build step |
| Skipped | Not built because the push didn't affect the project |
| Superseded | Not built because a newer commit on the branch was queued first |
| Spun down | Taken offline after Ready or Failed |
Production deployments also show Current when they serve your production domains, and Staged when they're Ready and waiting to be promoted. See Ready and Current.
Build queue
Each workspace runs a limited number of builds at once: 1 on Hobby and 3 on Pro. Further deployments wait as Queued and start in this order:
- Production deployments start before Preview deployments.
- Within each, the oldest queued deployment starts first.
- When you push a newer commit to a branch, that branch's older deployments that are still queued become Superseded, so only the latest commit builds. A deployment that's already building keeps building.
Time spent queued doesn't count toward build minutes. See Build pricing. If a build stops responding, Easel marks it Failed within about two minutes and starts the next queued deployment.
Cancel a deployment
Any workspace member can cancel a deployment that's Queued, Provisioning, Building, or Assigning domains. Canceling stops the build, keeps the logs written so far, and leaves stable URLs on the previous deployment. A Ready deployment can't be canceled, so spin it down instead.
Spin down a deployment
Spinning down takes a Ready or Failed deployment offline, and its unique URL stops serving. It's how you retire a deployment, since there's no separate delete action. Before spinning down the Current Production deployment, promote or roll back to another one.
Workflow runs still in progress on a deployment fail once it's spun down, because a run only continues on the deployment it started on. If it has any, you're asked first, and you can start them again on the latest deployment. See Workflows.
Deploy the same commit again
There's no action that rebuilds a past deployment with its original settings.
To build the same commit with current settings and variables, push it again,
run easel deploy from that revision, or promote a Ready Preview deployment of
it to production. Each of these creates a new deployment and leaves the original
unchanged.