Cloud Build for CI/CD in GCP - Step-by-Step Execution

Process Flow - Cloud Build for CI/CD

Code Commit to Repo

↓

Trigger Cloud Build

↓

Cloud Build Executes Steps

↓

Build, Test, Deploy

↓

Notify Success/Failure

↓

Code Deployed to Environment

Code is pushed to a repository, which triggers Cloud Build to run build, test, and deploy steps automatically, then notifies the result.

Execution Sample

GCP

steps:
- name: 'gcr.io/cloud-builders/docker'
  args: ['build', '-t', 'gcr.io/my-project/my-app', '.']
- name: 'gcr.io/cloud-builders/docker'
  args: ['push', 'gcr.io/my-project/my-app']
images:
- 'gcr.io/my-project/my-app'

This Cloud Build config builds a Docker image and pushes it to Google Container Registry.

Process Table

Step	Action	Command/Args	Result	Status
1	Start Build	Trigger received from repo commit	Build started	Success
2	Build Docker Image	docker build -t gcr.io/my-project/my-app .	Image built locally	Success
3	Push Docker Image	docker push gcr.io/my-project/my-app	Image pushed to registry	Success
4	Publish Image	images: gcr.io/my-project/my-app	Image available for deploy	Success
5	Build Complete	All steps finished	Build finished successfully	Success

💡 All build steps completed successfully, image ready for deployment

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
Build Status	Not started	Image built	Image pushed	Success
Docker Image	None	Built locally	Pushed to registry	Available
Trigger	No	Yes	Yes	Yes

Key Moments - 3 Insights

Why does Cloud Build start automatically after code commit?

Because a trigger is set up to listen to repository changes, as shown in Step 1 of the execution_table.

What happens if the docker build fails?

The build stops immediately and reports failure; subsequent steps like push won't run, which is why each step's status is important.

Why do we push the image after building it?

Pushing uploads the image to a registry so deployment systems can access it, as shown in Step 3 and Step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the status after Step 2?

A Success

B Failure

C Pending

D Skipped

💡 Hint

Check the 'Status' column for Step 2 in the execution_table.

At which step is the Docker image pushed to the registry?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Action' and 'Command/Args' columns in the execution_table.

If the trigger was not set, what would happen?

A Build would start automatically

B Build would not start after commit

C Build would fail at Step 2

D Image would not be pushed

💡 Hint

Refer to the 'Trigger' variable in variable_tracker and Step 1 in execution_table.

Concept Snapshot

Cloud Build automates CI/CD by running build steps on code commits.
Use triggers to start builds automatically.
Define steps in cloudbuild.yaml (build, test, deploy).
Images are built and pushed to registries.
Build status shows success or failure of each step.

Full Transcript

Cloud Build for CI/CD works by triggering a build when code is committed to a repository. The build runs defined steps such as building a Docker image and pushing it to a container registry. Each step's status is tracked to ensure success. If any step fails, the build stops. This automation helps deploy code changes quickly and reliably.