BuildsBuild status and lifecycle

Build status and lifecycle

A build is created, deployed, replaced by a newer build, and eventually deleted. This page follows a build through that cycle and covers what the dashboard shows at each stage.

The lifecycle at a glance#

1CreatedRegistered on the Builds page. Nothing runs yet.
→
2DeployedA deploy references it and runs its image as replicas.
→
3ReplacedDeploys move to a newer build. This one stays for rollback.
→
4DeletedRemoved once nothing uses it.

These stages describe how you use a build. The dashboard doesn't label them.

Build status#

The Builds page has no status column. A build is a record of an image reference and its resources. Creating one doesn't pull or build the image, so there's no build-time success or failure to show.

Problems with the image show up on the deploy instead, for example an image that can't be pulled, or a container that exits:

  • Pods shows each replica's Phase.
  • Watch logs on the deploy shows what the container printed.
  • The Restarts metric shows a crash-looping container.

See Deployment status and Troubleshooting.

1. Created#

You create a build from BuildsNew build. From then on it appears in every Build list for its project's deploys, shown as name:tag. See Create a build.

2. Deployed#

When a deploy uses the build, the deploy's replicas run its image with its CPU and memory request. The Deployments table shows the build in the Build column and its resources under Resources.

3. Replaced#

You ship a new version by creating a new build and pointing the deploy at it. The old build stays on the Builds page, so rolling back means pointing the deploy back at it. See Update and redeploy.

Two actions create a replacement build for you:

  • Adjust resources on a deploy creates a new build with the new CPU and memory, named after the old one with a version suffix (api becomes api-v2, api-v2 becomes api-v3), and moves the deploy to it.
  • Edit on the Builds page changes a build in place rather than creating a new one. See Manage builds.

4. Deleted#

Choose Delete on the Builds page and confirm Delete build "name"?. Delete builds that no deploy uses. To check, look for the build's name:tag in the Build column of the Deployments table.