Previously, when creating a new deployment with ZEIT Now, you were shown an
Initializingindicator that would be replaced with
Errordepending on whether the build succeeded
Today, we are removing this confusing initial state and are introducing more informative states for your deployments.
Before today's change, your deployments would only go through two different phases:
Initializing –> Ready or Error
Queued –> Building –> Ready or Error
When you create a new deployment it will first show up in a
Queuedstate, which indicates that the deployment scheduled to build but has not yet started:
Once a build container is available and selected, the deployment will automatically move into the
Your deployment queueing behind other deployments depends on the amount of Concurrent Builds your plan includes:
- Concurrent Builds on Free: 1
- Concurrent Builds on Pro: 3+
- Concurrent Builds on Business: 6+
- Concurrent Builds on Enterprise: Custom
On the Pro or Business plan, you increase the limit in your Billing settings:
As mentioned above, this state occurs once your deployment has started building:
After the build is complete, your deployment will be either marked as
Ready(the build successfully completed) or
Error(the build completed with an error).
The deployment section of our API documentation was adjusted accordingly. To opt-in to the new deployment states, you will need to use the latest version of all deployment endpoints.
With the new deployment states
Building, it's easier than ever to grasp which phase your deployment is in.
To take advantage of this update, either use:
Once you have tried it out, let us know what you think about this change!