Build triggers configuration in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the source repository for the build trigger.

GCP

{
  "triggerTemplate": {
    "projectId": "my-project",
    "repoName": [1],
    "branchName": "main"
  }
}

Drag options to blanks, or click blank then click option'

A"main"

B"build-config"

C"my-repo"

D"trigger-1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using branch name instead of repository name.

Using project ID instead of repository name.

The 'repoName' field must be the name of the source repository, such as "my-repo".

2fill in blank

medium

Complete the code to specify the branch filter for the build trigger.

GCP

{
  "triggerTemplate": {
    "projectId": "my-project",
    "repoName": "my-repo",
    "branchName": [1]
  }
}

Drag options to blanks, or click blank then click option'

A"develop"

B"my-repo"

C"feature-branch"

D"main"

Attempts:

3 left

💡 Hint

Common Mistakes

Using repository name instead of branch name.

Choosing a branch name that does not exist.

The 'branchName' field specifies which branch triggers the build, commonly "main".

3fill in blank

hard

Fix the error in the build trigger configuration by completing the missing field.

GCP

{
  "name": "my-trigger",
  "description": "Trigger on push to main",
  "triggerTemplate": {
    "projectId": "my-project",
    "repoName": "my-repo",
    [1]
  }
}

Drag options to blanks, or click blank then click option'

A"branchName": "main"

B"branchName": "develop"

C"tagName": "v1.*"

D"commitSha": "abc123"

Attempts:

3 left

💡 Hint

Common Mistakes

Using tagName or commitSha instead of branchName.

Omitting the branchName field.

The 'branchName' field is required to specify which branch triggers the build; here it should be "main".

4fill in blank

hard

Fill both blanks to complete the build trigger event configuration.

GCP

{
  "triggerTemplate": {
    "repoName": "my-repo",
    [1],
    [2]
  }
}

Drag options to blanks, or click blank then click option'

A"branchName": "main"

B"tagName": "v1.*"

C"projectId": "my-project"

D"commitSha": "abc123"

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing tagName or commitSha where projectId or branchName should be.

Omitting projectId or branchName.

The 'projectId' and 'branchName' fields are needed to specify the project and branch for the trigger.

5fill in blank

hard

Fill all three blanks to complete the build trigger filter and substitution configuration.

GCP

{
  "triggerTemplate": {
    [1],
    [2],
    "substitutions": {
      "_ENV": [3]
    }
  }
}

Drag options to blanks, or click blank then click option'

A"repoName": "my-repo"

B"branchName": "main"

C"production"

D"projectId": "my-project"

Attempts:

3 left

💡 Hint

Common Mistakes

Incorrect quoting of substitution value.

Missing projectId or branchName fields.

The trigger needs projectId, branchName, and a substitution value for _ENV set to "production".

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