Builds
What a build is, where to find it in the console, and how to read its status.
A build turns your source directory into a container image and stores it in your project's private registry. Every guidal deploy from a directory starts one, and so does an AI agent deploying from source.
Where builds appear
- Builds in the side navigation lists every build in the project, newest first, across all services. It also lists builds that never deployed: a build-only run, and the failed first build of a service that was therefore never created.
- Each web service and worker has its own Builds tab.
- Each build has its own page with its pipeline and its log. Open it from the build's id in either list.
Status
| Status | Meaning |
|---|---|
| Queued | Waiting to start |
| Submitting, Fetching source, Building, Pushing, Scanning, Signing | In progress; the build page shows each stage as it runs |
| Succeeded | The image is in your registry; a deploying build then rolls it out |
| Failed | A step or the platform failed; the build page says which, in words |
| Timed out | The build ran past your plan's time limit |
| Cancelled | Stopped before it finished |
The reasons a build can fail, and what to do about each one, are listed in Deploy from source.
From the CLI
bash
guidal builds list
guidal builds logs <build-id>