Deployments and logs
What happens during a build, what each status means and how to fix a failed deploy.
Statuses
| Status | Meaning |
|---|---|
| Queued | Accepted and waiting for a build slot |
| Building | Installing dependencies, building and starting the app |
| Ready | Live and serving traffic |
| Failed | A step stopped with an error. The previous version keeps serving |
| Cancelled | Stopped before it finished |
No downtime between versions
A new version is started next to the running one. Traffic switches only after it answers, then the old version stops. Visitors never hit a half-built release.
Redeploy and cancel
- Redeploy builds the project again with its current source, settings and variables. Use it after changing variables.
- Cancel stops a queued or building deployment.
- Open any older deployment to read its log and see which commit it built.
When a build fails
- 1Open the failed deployment and read the last lines of the log first. The error is almost always there.
- 2Check the detected framework and entry point at the top of the deployment.
- 3If Rimbra picked the wrong folder, set Root directory in Settings.
- 4If a command is wrong, set Install, Build or Start command in Settings.
- 5Fix the code or settings, then push again or choose Redeploy.