Deploy history and build log retention
See your recent deploys, open any single deploy for its full build log, status, and timing, and learn how long Voroa keeps build logs before they expire.
Every time you deploy — by pushing to your branch or using Manual Deploy — Voroa records it. The Deploys tab for your service shows this history, and each deploy has its own page with the full build log, so you can always go back and see what happened on a specific deploy.
View your recent deploys
Open your service and go to the Deploys tab. You will see your most recent deploys, newest first, with:
- The commit message and short commit hash for the deploy.
- The Status — for example Live, Building, Starting, Failed, or Build failed. See Deploy status for what each one means.
- The Trigger — whether the deploy came from a push to GitHub or a manual deploy.
- The Duration — how long the deploy took.
You can search your deploys by commit message or hash, and filter by status, to quickly find the one you are looking for.
Open a single deploy
Click any deploy in the list to open its own page. The deploy page shows, at a glance:
- Status — the live status of that deploy. While a deploy is in progress this updates on its own, moving from Building to Starting to Live (or to Failed if something goes wrong).
- Source — the commit that was deployed.
- Trigger — how the deploy was started.
- Duration — the total time the deploy took.
Below that is the full build log for the deploy. If the deploy is still running, the log streams live as the build progresses. Once the deploy finishes, the log stays available so you can review exactly what the build did.
How long build logs are kept
Voroa keeps build logs for a limited time — currently 7 days. This keeps your dashboard fast and your storage in check, and it matches how most cloud platforms handle logs.
After the retention window:
- The deploy still appears in your history, with its status, commit, trigger, and duration intact — nothing is removed from the list.
- Its build log is no longer available. Opening an older deploy shows a clear message that the log is past the retention window, instead of an empty screen.
If you want a permanent record of a build, copy the log while the deploy is recent, or trigger a fresh deploy to generate a new build you can review.