Builds and deploy logs
Developers and operators monitoring deploys on tnc-sh.cloud projects.
Use the Builds page and environment log panels to follow deploy progress, diagnose failures, and decide when to rebuild versus change branch mappings.
Every deploy creates a build record with status, commit SHA, branch name, and streaming logs. This guide shows where to find them and how to act on common outcomes.
4 sections4 key takeaways3 related guides
Quick highlights
Every deploy creates a build record with status, commit SHA, branch name, and streaming logs. This guide shows where to find them and how to act on common outcomes.
Start with the Builds list for history, then drill into environment logs when a specific stack is misbehaving after a successful build.
What you will learn
- Builds are scoped per project — filter by environment and branch from the Builds page.
- Install logs capture provisioning and Odoo setup; runtime logs live under Environments.
- Rebuild reruns the current mapped branch; fix mapping or refs before repeated retries.
- Copy build ID and log excerpts into support tickets for faster triage.
Sections in this guide