Cloud Build API

Name: Cloud Build API API
Brand: Cloud Build API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi Cdoauth240 EndpointsREST

For Agents

Trigger, monitor, and manage Google Cloud Build CI/CD pipelines, including build triggers, worker pools, and GitHub webhook integration. Useful for automated build, test, and image-publishing workflows on GCP.

Quickstart

Get started with Cloud Build API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a google cloud build"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloud Build API API.

Submit a build directly to Cloud Build with inline build steps and source

Create build triggers that fire on push, pull-request, or tag events from GitHub or Cloud Source Repositories

Cancel a running build or retry a failed build by ID

Provision and manage private worker pools for builds that need VPC access

GET STARTED

Start building with Cloud Build API API

Explore with Jentic

View OpenAPI Document

Use for: I need to trigger a Cloud Build pipeline for the main branch of my repo, Cancel a runaway build that has been running for over an hour, List all builds that failed in the last 24 hours for my project, Set up a trigger that fires whenever a pull request is opened in our GitHub repo

Not supported: Does not deploy artifacts to runtime environments, host source repositories, or store built images — use for build, test, and trigger orchestration only.

Google Cloud Build is a managed continuous-integration service that compiles source code, runs tests, and produces container images or other artifacts on Google Cloud. The API exposes builds, build triggers, worker pools, and GitHub webhook integration so agents can launch builds on demand, configure triggers that fire on Git events, and inspect build logs and status. Builds run in isolated VMs with configurable machine size and private worker pools for builds that need access to internal networks.

Use Cases

Patterns agents use Cloud Build API API for, with concrete tasks.

★ GitHub-Driven Container Build Pipeline

Engineering teams use Cloud Build triggers to build and push container images on every commit to a GitHub repository. The trigger watches a branch pattern, runs a cloudbuild.yaml that builds the Dockerfile, runs tests, and pushes the resulting image to Artifact Registry. Setup takes under an hour for a single repo and triggers can be templated across many services.

Call POST /v1/projects/{projectId}/triggers with a github filter on branch=main and a build configuration that builds and pushes to us-docker.pkg.dev

On-Demand Build for Release Candidates

Release engineers fire builds on demand to produce a release candidate image for a specific tag. The runTrigger operation accepts the trigger ID and a substitutions map (TAG_NAME, COMMIT_SHA), kicks off the build, and returns a long-running operation the caller can poll. Common in release-pipeline orchestration where the build is one step in a larger workflow.

Call POST /v1/projects/{projectId}/triggers/{triggerId}:run with branchName=release/v1.4.0 and TAG_NAME substitution

Build Status Reporting and Failure Triage

On-call engineers and dashboards call the builds list and get endpoints to surface the status of recent builds, identify failures, and cancel runaway jobs. Filters by status (FAILURE, TIMEOUT) and trigger ID make it easy to attribute breakages to specific pipelines.

Call GET /v1/projects/{projectId}/builds?filter=status="FAILURE" and cancel any build older than one hour via /builds/{id}:cancel

AI Agent Release Operator via Jentic

An agent invoked by a release operator searches Jentic for the right Cloud Build operation, fires the release trigger with the correct tag, polls for completion, and reports the resulting image digest. The agent never sees the underlying service account key — Jentic injects a scoped token at execution time.

Search Jentic for 'run google cloud build trigger', execute against /triggers/{triggerId}:run with TAG_NAME substitution, then poll /builds/{id} until status is SUCCESS

Key Endpoints

40 endpoints — google cloud build is a managed continuous-integration service that compiles source code, runs tests, and produces container images or other artifacts on google cloud.

METHOD

PATH

DESCRIPTION

POST

/v1/projects/{projectId}/builds

Submit a new build

GET

/v1/projects/{projectId}/builds

List builds for a project

POST

/v1/projects/{projectId}/builds/{id}:cancel

Cancel a running build

POST

/v1/projects/{projectId}/builds/{id}:retry

Retry a failed build

POST

/v1/projects/{projectId}/triggers

Create a build trigger

POST

/v1/projects/{projectId}/triggers/{triggerId}:run

Run a build trigger on demand

POST

/v1/githubDotComWebhook:receive

Receive a GitHub webhook event

POST

/v1/projects/{projectId}/builds

Submit a new build

GET

/v1/projects/{projectId}/builds

List builds for a project

POST

/v1/projects/{projectId}/builds/{id}:cancel

Cancel a running build

POST

/v1/projects/{projectId}/builds/{id}:retry

Retry a failed build

POST

/v1/projects/{projectId}/triggers

Create a build trigger

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Cloud OAuth 2.0 credentials and service account keys are stored encrypted in the Jentic vault. Agents receive short-lived access tokens scoped to cloud-platform — raw service account JSON never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'trigger google cloud build' or 'cancel cloud build') and Jentic returns the matching operation with its parameter schema, so the agent can call the right endpoint without reading Discovery docs.

Time to first call

Direct Cloud Build integration: 2-4 days for OAuth, trigger configuration, and long-running operation polling. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Artifact Registry API

Stores the container images and language packages that Cloud Build produces

Use Cloud Build to build and push images; use Artifact Registry to list, tag, or delete the resulting artifacts

Complementary

GitHub REST API

Source-control side of GitHub-driven Cloud Build triggers

Use the GitHub API to read or comment on the commit that fired a build; use Cloud Build to inspect or rerun the build itself

Complementary

Cloud Deploy API

Promotes the artifacts produced by Cloud Build through staged delivery pipelines

Use Cloud Build for build-and-test; use Cloud Deploy when the pipeline continues into staged GKE or Cloud Run rollouts

Alternative

GitLab REST API

Self-hosted or SaaS Git platform with its own pipeline product

Choose GitLab CI when source lives in GitLab; choose Cloud Build when source lives in GitHub or Cloud Source Repositories and target is GCP

FAQs

Specific to using Cloud Build API API through Jentic.

What authentication does the Cloud Build API use?

The Cloud Build API uses OAuth 2.0 with the cloud-platform scope. Tokens are issued for a Google service account or an end user. Through Jentic, the OAuth credential lives in the Jentic vault and the agent receives a short-lived access token only — the underlying service account JSON never enters agent context.

Can I trigger a Cloud Build pipeline from outside Google Cloud?

Yes. Either POST /v1/projects/{projectId}/builds with an inline build spec, or call /triggers/{triggerId}:run on an existing trigger. For GitHub-driven flows, configure the githubDotComWebhook receiver and the trigger fires automatically on each push or pull request.

What are the rate limits for the Cloud Build API?

Cloud Build quotas are published per-method in the Google Cloud console under the Cloud Build quota page; typical defaults are several hundred build creations per minute per project, with separate concurrent-build quotas based on machine type and worker pool size.

How do I cancel a running build through Jentic?

Search Jentic for 'cancel google cloud build' and execute the operation against POST /v1/projects/{projectId}/builds/{id}:cancel with the build ID. The build transitions to CANCELLED and any active step is terminated immediately.

Does Cloud Build support builds in a private VPC?

Yes. Create a private worker pool via the workerPools resource, attach it to a VPC peering, and reference the worker pool in the build's options.pool field. Builds running on the pool can reach internal Artifact Registry repos, private GitHub Enterprise instances, and other VPC-only services.

Is Cloud Build free?

Cloud Build includes a free tier of 120 build minutes per day on the smallest machine type; usage beyond that and any private worker pool runtime is billed per build minute as documented on the Cloud Build pricing page.