Skip to main content

GCP Cloud Build Build

A Cloud Build Build represents a single execution of Google Cloud Build, Google Cloud’s CI/CD service. A build encapsulates the full specification of the steps to run, the images to use, the source to fetch, the artefacts to produce, and the logs generated while the build is running. Once created, the build resource tracks the lifecycle of the execution (QUEUED → WORKING → SUCCESS/FAILURE/etc.) and records metadata such as timing information, substitutions and provenance.
Official documentation: https://cloud.google.com/build/docs/api/reference/rest/v1/projects.builds

Supported Methods​

  • GET: Get a gcp-cloud-build-build by its "name"
  • LIST: List all gcp-cloud-build-build
  • SEARCH

gcp-logging-bucket​

Cloud Build writes execution logs to Cloud Logging. If an aggregated sink routes those logs to a specific Logging bucket, the build will be linked to that gcp-logging-bucket as the destination of its logs.

gcp-iam-service-account​

Every build runs under a service account (by default [PROJECT_NUMBER]@cloudbuild.gserviceaccount.com, or a user-specified one). The build will therefore be linked to the gcp-iam-service-account that provided its runtime identity and permissions.

gcp-storage-bucket​

Builds can pull source code from Cloud Storage, upload artefacts or logs to a bucket, and use buckets for caching. Any bucket referenced in the build’s source, artifacts, logsBucket, or step arguments will appear as a related gcp-storage-bucket.

gcp-artifact-registry-docker-image​

A common outcome of a Cloud Build is a container image pushed to Artifact Registry. When a build either pulls a base image from, or pushes a resulting image to, Artifact Registry, Overmind links the build to the corresponding gcp-artifact-registry-docker-image to surface that dependency.