Cloud Build Basics
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Cloud Build Basics provides a foundational guide to using Google Cloud's serverless CI/CD platform. It covers the essential concepts of build configurations, triggers, and artifacts. The skill walks users through the necessary prerequisites, such as API enablement and authentication, and provides step-by-step instructions for creating automated build triggers and manually executing builds via both the Google Cloud Console and the gcloud CLI.
What it does
- Explains core Cloud Build concepts like cloudbuild.yaml, build steps, and triggers.
- Guides users through enabling the Cloud Build API and configuring project authentication.
- Provides instructions for navigating the Build History page to monitor build status and logs.
- Details the workflow for creating automated triggers based on repository events.
- Demonstrates how to manually run existing triggers using the console or command line.
- Includes guidance on overriding substitution variables during manual trigger execution.
When to use it
- When you are new to Google Cloud Build and need to understand its basic workflow.
- When you need to set up a simple automated build trigger for a repository.
- When you need to manually trigger a build or debug a failed build via logs.
- When you require a quick reference for basic gcloud commands related to Cloud Build.
Advantages
- Provides a clear, structured path for beginners to get started with Cloud Build.
- Covers both GUI-based and CLI-based workflows for flexibility.
- Includes essential troubleshooting tips like accessing build logs.
- Emphasizes best practices like using service accounts for production environments.
Usage examples
- “How do I enable the Cloud Build API for my project?”
- The agent will provide the gcloud command to enable the cloudbuild.googleapis.com service and verify project context.
- “Show me how to manually run a build trigger named my-trigger in the global region.”
- The agent will provide the gcloud builds triggers run command with the appropriate flags for the trigger name and region.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/cloud-build-basics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip cloud-build-basics.zip -d .agents/skills
Documentation by Google
Cloud Build Basics
Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read Usage Attribution. For commands executed
directly in the terminal (never in generated scripts, Terraform, or user code),
prefix gcloud with
CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:cloud-build-basics)"
and append agent-skills/1.0 (skill:cloud-build-basics) to User-Agent headers.
Prerequisites
Before starting, ensure the following prerequisites are met:
Google Cloud SDK: Ensure the Google Cloud SDK is installed and configured.
Authentication: Authenticate the gcloud CLI:
gcloud auth login gcloud auth application-default loginProject ID: Know the target Google Cloud Project ID. Set the context:
gcloud config set project <PROJECT_ID>Enable Cloud Build API: The Cloud Build API must be enabled for the project.
gcloud services enable cloudbuild.googleapis.comPermissions: Ensure the user or service account has the necessary permissions, such as
roles/cloudbuild.builds.editorandroles/serviceusage.serviceUsageAdmin(to enable the API).
Core Concepts
Cloud Build (GCB) is a serverless platform that executes your builds on Google Cloud. It translates your source code into deployable artifacts, such as Docker containers or Java archives.
| Concept | Description |
|---|---|
cloudbuild.yaml | The required configuration file that defines the build steps. It is written in YAML or JSON. |
| Build Steps | A sequence of actions (steps) GCB performs. Each step runs a command inside a specific Docker container (the builder). Common builders include gcr.io/cloud-builders/gcloud, gcr.io/cloud-builders/docker, and custom containers. |
| Artifacts | The output of the build, typically a container image pushed to Google Container Registry (GCR) or Artifact Registry (AR), or other deployable files. |
| Triggers | Automation rules that invoke a build in response to an event, such as a push to a Git repository, a Pub/Sub message, or a manual request. |
Navigation: Viewing Build History
The Cloud Build Build History page is the central place to monitor the status of past and ongoing builds.
Open the Cloud Console: Navigate to the Google Cloud Console.
Go to Cloud Build: Use the search bar or the navigation menu to find Cloud Build.
Select Build History: In the left navigation pane, select History (or use the direct URL:
https://console.cloud.google.com/cloud-build/builds).Review Builds:
Status: Check the status column (
SUCCESS,FAILURE,WORKING,QUEUED).Region: Use the region filter at the top to view builds that ran in a specific region (important for regional worker pools).
Logs: Click on a specific Build ID to view the detailed logs, execution steps, and build summary. This is crucial for debugging failed builds.
[!NOTE] If this is your first time visiting the page, you might see the "zero-state" experience, which offers options to run a sample build or create your first trigger (as noted in the
cb-list-build-zero-stateskill). Note that region settings for triggers and builds are immutable after creation and must be chosen deliberately.
Creating a Basic Automated Trigger
This process defines an automation rule to run a build whenever code is pushed to a specified Git branch.
Step 1: Start Trigger Creation
Navigate to the Cloud Build Triggers page (
https://console.cloud.google.com/cloud-build/triggers).Click Create trigger.
Step 2: Configure Trigger Settings
Name: Provide a unique, descriptive name (e.g.,
github-main-branch-build).Region: Select the region where the trigger configuration will be stored (e.g.,
globalor a specific regional endpoint). Note: Trigger and build region settings are immutable after creation and must be chosen deliberately.Event: Select the event type. For automated CI/CD, select Push to a branch.
Source: Select the repository source:
Repository: Connect your source repository (GitHub, Bitbucket, Cloud Source Repositories, etc.). If needed, authorize the connection.
Repository Name: Select the specific repository you want to link.
Branch: Enter the branch pattern (e.g.,
^main$or^develop).
Step 3: Configure Build Settings
Configuration: Select Cloud Build configuration file (yaml or json).
Location: Keep the default Repository and specify the path to your build configuration file (e.g.,
cloudbuild.yaml).Alternative: For very simple builds, you can choose Inline to paste the YAML configuration directly into the trigger.
(Optional) Service Account: For production environments, select a dedicated service account with limited permissions to enforce the principle of least privilege.
Step 4: Save and Test
Click Create. The trigger is now active and will run automatically on the next matching Git push.
[!TIP] The
cb-create-triggerskill provides detailedgcloudcommands for creating triggers across all types (GitHub, Pub/Sub, Webhook) and configurations (inline, Dockerfile, YAML). Use that skill for CLI automation.
Running an Existing Trigger Manually
Sometimes you need to run a trigger on demand, outside of its normal automation flow (e.g., to rebuild an old commit or test a new substitution).
[!IMPORTANT] Substitution Immutability: You can only override values for substitution variables that are already defined in the trigger configuration. You cannot introduce new substitution variable keys at runtime.
Option A: Via the Cloud Console
Navigate to the Cloud Build Triggers page (
https://console.cloud.google.com/cloud-build/triggers).Locate the trigger you wish to run.
Click the vertical ellipsis (⋮) next to the trigger and select Run.
A dialog will appear, allowing you to specify:
Source branch/tag: Choose the specific Git reference to build from.
Substitution Variables: Override any existing substitution variables (e.g., set
_VERSIONto a new value).
Click Run trigger. The build will start immediately, and you can monitor its status on the History page.
Option B: Via the gcloud CLI
Use the gcloud builds triggers run command to invoke the trigger and optionally override parameters.
# Run the trigger against the 'main' branch
gcloud builds triggers run <TRIGGER_NAME> \
--region=<REGION> \
--branch=main
# Run the trigger and override a substitution variable
gcloud builds triggers run <TRIGGER_NAME> \
--region=<REGION> \
--branch=main \
--substitutions=_IMAGE_TAG="20231027-manual"
# Monitor the initiated build
# Note: The run command outputs the build ID. Use it to check status:
# gcloud builds log <BUILD_ID> --region=<REGION>[!NOTE] The
cb-run-triggerskill provides more complex invocation examples, including running against a specific commit SHA or using tags.
Related Skills
cb-create-trigger: Detailed CLI-focused instructions for creating all trigger types.cb-list-build-zero-state: Advanced management of the Cloud Build dashboard and onboarding zero state.cb-run-trigger: Comprehensive guide to manually running triggers using variousgcloudoptions.
External Resources & Documentation
Files
- ATTRIBUTION.mdAdded by AutoGineer854 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md8.4 KiB
- references/attribution.md1.8 KiB
- references/cb-create-trigger.md11.6 KiB
- references/cb-list-build-zero-state.md7.2 KiB
- references/cb-run-trigger.md5.9 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/cloud-build-basics · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cloud-build-basics.zip