Why Build triggers configuration in GCP? - Purpose & Use Cases

The Big Idea

What if your code could build itself every time you save a change?

The Scenario

Imagine you have a project where every time you update your code, you must manually start the build process by logging into your cloud console and clicking buttons.

This means waiting, switching screens, and hoping you didn't forget any step.

The Problem

Manually starting builds is slow and easy to forget.

It causes delays and mistakes, like building the wrong version or missing important updates.

It's like having to call your friend every time you want to turn on the lights at home instead of using a switch.

The Solution

Build triggers automatically start your build whenever you push code or make changes.

This means no waiting, no manual clicks, and your builds always run on time.

It's like having a smart home system that turns on lights as soon as you enter a room.

Before vs After

✗ Before

Go to Cloud Console > Select project > Click 'Start Build' > Wait

✓ After

Create trigger linked to repo > Push code > Build starts automatically

What It Enables

Build triggers let you focus on coding while your cloud handles building instantly and reliably.

Real Life Example

When a developer pushes a fix to the main branch, the build trigger runs tests and deploys the app without any extra steps.

Key Takeaways

Manual builds waste time and cause errors.

Build triggers automate and speed up the process.

They ensure your code is always built and tested right after changes.

Practice

1. What is the main purpose of a build trigger in Google Cloud Build?

easy

A. To monitor server health

B. To manually deploy an application

C. To automatically start a build when code changes occur

D. To create a new repository

Solution

1. Step 1: Understand build triggers role

   Build triggers watch for code changes and start builds automatically.

2. Step 2: Compare options with purpose

   Only To automatically start a build when code changes occur describes automatic build start on code changes.

3. Final Answer:

   To automatically start a build when code changes occur -> Option C

4. Quick Check:

   Build trigger = auto build start [OK]

Hint: Build triggers start builds automatically on code changes [OK]

Common Mistakes:

• Confusing triggers with manual deployment
• Thinking triggers monitor servers
• Assuming triggers create repositories

2. Which of the following is the correct syntax to specify a branch filter in a Cloud Build trigger YAML?

easy

A. trigger:
branchName: "^main$"

B. trigger:
branchName: "main"

C. trigger:
branch: "main"

D. trigger:
branchFilter: "main"

Solution

1. Step 1: Identify correct branch filter syntax

   Cloud Build uses regex in branchName to filter branches.

2. Step 2: Match regex syntax for main branch

   "^main$" matches exactly the main branch name.

3. Final Answer:

   trigger: branchName: "^main$" -> Option A

4. Quick Check:

   branchName uses regex = trigger: branchName: "^main$" [OK]

Hint: Use regex in branchName to filter branches [OK]

Common Mistakes:

• Using branch instead of branchName
• Not using regex anchors ^ and $
• Using incorrect field like branchFilter

3. Given this trigger configuration snippet:

trigger:
  branchName: "^release-.*$"
  build:
    steps:
    - name: "gcr.io/cloud-builders/docker"
      args: ["build", "-t", "gcr.io/my-project/my-app:$SHORT_SHA", "."]

What happens when a commit is pushed to branch release-v1.2?

medium

A. The build fails due to syntax error

B. The build starts and tags the image with the commit SHA

C. The build starts but tags the image with 'latest'

D. The build does not start because branch name does not match

Solution

1. Step 1: Check branchName regex against branch

   Regex "^release-.*$" matches any branch starting with 'release-', so 'release-v1.2' matches.

2. Step 2: Understand build step and tagging

   The build uses $SHORT_SHA to tag the image, so image is tagged with commit SHA.

3. Final Answer:

   The build starts and tags the image with the commit SHA -> Option B

4. Quick Check:

   Branch matches regex and tags with SHA = The build starts and tags the image with the commit SHA [OK]

Hint: Regex matches branch, build tags image with commit SHA [OK]

Common Mistakes:

• Assuming branch does not match regex
• Thinking image tags as 'latest'
• Confusing syntax error with correct YAML

4. You configured a build trigger with this YAML snippet:

trigger:
  branchName: "main"
  build:
    steps:
    - name: "gcr.io/cloud-builders/gcloud"
      args: ["app", "deploy"]

But the build never starts when you push to main. What is the likely error?

medium

A. The build steps are missing the Docker build command

B. The trigger YAML is missing the substitutions field

C. The trigger must specify a tagName instead of branchName

D. branchName should be a regex like "^main$"

Solution

1. Step 1: Check branchName format in trigger

   Cloud Build expects branchName as a regex pattern, not plain string.

2. Step 2: Correct branchName to regex

   Changing branchName to "^main$" matches exactly the main branch and triggers build.

3. Final Answer:

   branchName should be a regex like "^main$" -> Option D

4. Quick Check:

   branchName needs regex = branchName should be a regex like "^main$" [OK]

Hint: branchName must be regex, not plain text [OK]

Common Mistakes:

• Using plain branch name without regex anchors
• Confusing branchName with tagName
• Thinking substitutions are mandatory

5. You want to create a build trigger that starts only when a tag matching v* is pushed, and the build should run two steps: first build a Docker image, then deploy it. Which YAML snippet correctly configures this trigger?

hard

A. trigger:
tagName: "^v.*$"
build:
steps:
- name: "gcr.io/cloud-builders/docker"
args: ["build", "-t", "gcr.io/my-project/my-app:$TAG_NAME", "."]
- name: "gcr.io/cloud-builders/gcloud"
args: ["app", "deploy"]

B. trigger:
branchName: "^v.*$"
build:
steps:
- name: "gcr.io/cloud-builders/docker"
args: ["build", "-t", "gcr.io/my-project/my-app:$TAG_NAME", "."]
- name: "gcr.io/cloud-builders/gcloud"
args: ["app", "deploy"]

C. trigger:
tagName: "v*"
build:
steps:
- name: "gcr.io/cloud-builders/gcloud"
args: ["app", "deploy"]

D. trigger:
tagName: "^v.*$"
build:
steps:
- name: "gcr.io/cloud-builders/docker"
args: ["build", "-t", "gcr.io/my-project/my-app:latest", "."]

Solution

1. Step 1: Identify correct tag filter syntax

   Use tagName with regex "^v.*$" to match tags starting with 'v'.

2. Step 2: Verify build steps order and commands

   First step builds Docker image tagged with $TAG_NAME, second step deploys app.

3. Step 3: Check for errors in other options

   trigger: branchName: "^v.*$" build: steps: - name: "gcr.io/cloud-builders/docker" args: ["build", "-t", "gcr.io/my-project/my-app:$TAG_NAME", "."] - name: "gcr.io/cloud-builders/gcloud" args: ["app", "deploy"] uses branchName instead of tagName, C misses Docker build step, D tags image as latest without deploy step.

4. Final Answer:

   trigger: tagName: "^v.*$" build: steps: - name: "gcr.io/cloud-builders/docker" args: ["build", "-t", "gcr.io/my-project/my-app:$TAG_NAME", "."] - name: "gcr.io/cloud-builders/gcloud" args: ["app", "deploy"] -> Option A

5. Quick Check:

   tagName regex and two steps build+deploy = trigger: tagName: "^v.*$" build: steps: - name: "gcr.io/cloud-builders/docker" args: ["build", "-t", "gcr.io/my-project/my-app:$TAG_NAME", "."] - name: "gcr.io/cloud-builders/gcloud" args: ["app", "deploy"] [OK]

Hint: Use tagName regex and list all build steps in order [OK]

Common Mistakes:

• Using branchName instead of tagName for tags
• Missing one of the required build steps
• Incorrect tagName regex syntax