Google Cloud Build API
Browse all Google APIs40
AI ReadinessFoundational (D-)40/100
Official vendor OpenAPI document · agent-readyDeveloper 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.
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.
Install Jentic One Beta
Connect the Cloud Build API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Build API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fcloudbuild" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fcloudbuild" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Cloud Build 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
List historical builds for a project with pagination and filtering
Receive GitHub webhook events at the githubDotComWebhook endpoint to drive build triggers
Run a build trigger on demand with a specified branch or tag substitution
Use Cases
Patterns agents use Cloud Build 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
POST
/v1/projects/{projectId}/triggers/{triggerId}:run
Run a build trigger on demand
POST
/v1/githubDotComWebhook:receive
Receive a GitHub webhook event
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Cloud Build API
- Foundational (D-)40/100
45
Foundational Compliance56
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability63
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
45
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
57%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
21%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
77%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Cloud Build by hand means setting up Google OAuth 2.0, minting short-lived access tokens against the cloud-platform scope, and pointing every call at cloudbuild.googleapis.com yourself. Through Jentic you install once, import the Cloud Build API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Cloud Build puts the project and build ids in the URL path (/v1/projects/{projectId}/builds/{id}), so a rule can pin your agent to one project: it can create and list builds and run triggers there and nothing else. You choose the operations it may call, so build cancellation or trigger deletion are not included unless you add them.
Credential isolation
Your Cloud Build OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'trigger a Google Cloud build' or 'cancel a running build', and Jentic returns the matching Cloud Build operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Build 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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Cloud Build API?
Yes. Because Jentic One is self-hosted, your own rules decide which Cloud Build operations and credentials the agent may use. Since Cloud Build puts the project and build IDs in the URL path (/v1/projects/{projectId}/builds/{id}), you can pin the agent to a single project so it only creates and lists builds and runs triggers there and nothing else. You choose the exact operations it can call, so sensitive actions like build cancellation or trigger deletion stay off limits unless you explicitly grant them.
GET STARTED