Cloud Build for CI/CD in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the build steps in a Cloud Build configuration file.

GCP

steps:
  - name: 'gcr.io/cloud-builders/[1]'
    args: ['build', '-t', 'gcr.io/my-project/my-image', '.']

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

Akubectl

Bdocker

Cgcloud

Dbash

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kubectl' instead of 'docker' for building images.

Using 'gcloud' which is for Google Cloud CLI, not building images.

The docker builder is used to build Docker images in Cloud Build steps.

2fill in blank

medium

Complete the code to trigger a build on a push to the main branch.

GCP

triggerTemplate:
  branchName: '[1]'
  repoName: 'my-repo'

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

Arelease

Bfeature

Cdevelop

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using a feature branch name which is not the main branch.

Using 'develop' which is often used for development but not production triggers.

The build trigger activates when code is pushed to the main branch.

3fill in blank

hard

Fix the error in the Cloud Build YAML to correctly specify the image push step.

GCP

steps:
  - name: 'gcr.io/cloud-builders/docker'
    args: ['[1]', 'gcr.io/my-project/my-image']

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

Apush

Bpull

Cbuild

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pull' which downloads images instead of uploading.

Using 'run' which executes containers, not pushes images.

The push command uploads the built image to the container registry.

4fill in blank

hard

Fill both blanks to define a substitution variable and use it in the build args.

GCP

substitutions:
  _IMAGE_TAG: '[1]'
steps:
  - name: 'gcr.io/cloud-builders/docker'
    args: ['build', '-t', 'gcr.io/my-project/my-image:[2]', '.']

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

Av1.0.0

Blatest

Cv2.1.3

Dstable

Attempts:

3 left

💡 Hint

Common Mistakes

Using different values for substitution and image tag causing mismatch.

Using 'latest' which is a moving tag, not a fixed version.

The substitution variable _IMAGE_TAG is set to 'v1.0.0' and used in the image tag.

5fill in blank

hard

Fill all three blanks to configure a Cloud Build step that runs tests, stores results, and sets a timeout.

GCP

steps:
  - name: 'gcr.io/cloud-builders/[1]'
    args: ['test']
    id: 'run-tests'
    waitFor: ['-']
    timeout: '[2]s'
artifacts:
  objects:
    location: 'gs://my-bucket/test-results'
    paths: ['[3]']

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

Anpm

Bpytest

Ctest-results.xml

D600

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'npm' which is for Node.js but not the test runner here.

Setting timeout too low or too high without matching the options.

Incorrect artifact path causing missing test results.

The step uses the pytest builder to run tests, sets a 600 second timeout, and stores results in 'test-results.xml'.

Practice

1. What is the primary purpose of Google Cloud Build in a CI/CD pipeline?

easy

A. To store large amounts of data

B. To automate building, testing, and deploying code

C. To monitor network traffic

D. To manage user permissions

Solution

1. Step 1: Understand Cloud Build's role

   Cloud Build automates the process of building, testing, and deploying code, which is essential in CI/CD pipelines.

2. Step 2: Eliminate unrelated options

   Storing data, monitoring network traffic, and managing permissions are not primary functions of Cloud Build.

3. Final Answer:

   To automate building, testing, and deploying code -> Option B

4. Quick Check:

   Cloud Build = Automate build/test/deploy [OK]

Hint: Remember: Cloud Build automates code delivery steps [OK]

Common Mistakes:

• Confusing Cloud Build with storage services
• Thinking Cloud Build manages network or permissions
• Assuming Cloud Build only builds code without testing or deploying

2. Which of the following is the correct way to specify a build step in a Cloud Build YAML file?

easy

A. actions:
- image: 'docker'
run: ['build', '-t', 'image', '.']

B. build_steps:
- container: 'gcr.io/cloud-builders/docker'
commands: ['build', '-t', 'image', '.']

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

D. commands:
- use: 'docker'
execute: ['build', '-t', 'image', '.']

Solution

1. Step 1: Review Cloud Build YAML syntax

   The correct key for build steps is 'steps', and each step uses 'name' for the builder image and 'args' for commands.

2. Step 2: Compare options to syntax

   steps: - name: 'gcr.io/cloud-builders/docker' args: ['build', '-t', 'gcr.io/my-project/my-image', '.'] matches the correct syntax. Other options use incorrect keys like 'build_steps', 'actions', or 'commands'.

3. Final Answer:

   steps: - name: 'gcr.io/cloud-builders/docker' args: ['build', '-t', 'gcr.io/my-project/my-image', '.'] -> Option C

4. Quick Check:

   Use 'steps' with 'name' and 'args' in Cloud Build YAML [OK]

Hint: Look for 'steps' with 'name' and 'args' keys in YAML [OK]

Common Mistakes:

• Using wrong keys like 'build_steps' or 'actions'
• Confusing 'args' with 'commands'
• Omitting the builder image name

3. Given this Cloud Build YAML snippet, what will be the output of the build step?

steps:
- name: 'ubuntu'
  args: ['echo', 'Hello, Cloud Build!']

medium

A. Build fails due to missing Docker image

B. Syntax error in YAML file

C. No output is produced

D. Hello, Cloud Build!

Solution

1. Step 1: Analyze the build step

   The step uses the 'ubuntu' image and runs the command 'echo Hello, Cloud Build!'. This command prints the message to the output.

2. Step 2: Determine expected output

   Since 'echo' prints text, the output will be 'Hello, Cloud Build!'. There is no syntax error or missing image because 'ubuntu' is a valid public image.

3. Final Answer:

   Hello, Cloud Build! -> Option D

4. Quick Check:

   Echo command prints text output [OK]

Hint: Echo commands print their arguments as output [OK]

Common Mistakes:

• Assuming build fails due to image name
• Thinking no output is produced by echo
• Confusing YAML syntax errors with valid syntax

4. You wrote this Cloud Build YAML but the build fails immediately. What is the error?

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

medium

A. Missing the build context (dot) at the end of args

B. Incorrect builder image name

C. YAML indentation error

D. args should be a string, not a list

Solution

1. Step 1: Check Docker build command syntax

   The Docker build command requires a build context, usually '.' at the end, to specify where to find the Dockerfile.

2. Step 2: Identify missing argument

   The args list misses the '.' context argument, causing the build to fail immediately.

3. Final Answer:

   Missing the build context (dot) at the end of args -> Option A

4. Quick Check:

   Docker build needs context path '.' [OK]

Hint: Always end docker build args with '.' for context [OK]

Common Mistakes:

• Assuming image name is wrong
• Thinking YAML indentation is the issue
• Using string instead of list for args

5. You want to create a Cloud Build pipeline that builds a Docker image, runs tests, and then deploys only if tests pass. Which YAML structure correctly represents this workflow?

hard

A. steps:
- name: 'gcr.io/cloud-builders/docker'
args: ['build', '-t', 'gcr.io/my-project/my-image', '.']
- name: 'gcr.io/cloud-builders/docker'
args: ['run', 'my-image', 'test']
waitFor: ['-']
- name: 'gcr.io/cloud-builders/gcloud'
args: ['app', 'deploy']
waitFor: ['-']

B. steps:
- name: 'gcr.io/cloud-builders/docker'
args: ['build', '-t', 'gcr.io/my-project/my-image', '.']
waitFor: ['-']
- name: 'gcr.io/cloud-builders/docker'
args: ['run', 'my-image', 'test']
waitFor: ['-']
- name: 'gcr.io/cloud-builders/gcloud'
args: ['app', 'deploy']

C. steps:
- name: 'gcr.io/cloud-builders/docker'
args: ['build', '-t', 'gcr.io/my-project/my-image', '.']
- name: 'gcr.io/cloud-builders/docker'
args: ['run', 'my-image', 'test']
- name: 'gcr.io/cloud-builders/gcloud'
args: ['app', 'deploy']

D. steps:
- name: 'gcr.io/cloud-builders/docker'
args: ['build', '-t', 'gcr.io/my-project/my-image', '.']
- name: 'gcr.io/cloud-builders/docker'
args: ['run', 'my-image', 'test']
- name: 'gcr.io/cloud-builders/gcloud'
args: ['app', 'deploy']
waitFor: ['-']

Solution

1. Step 1: Understand step dependencies in Cloud Build

   Cloud Build starts steps in parallel by default. Use 'waitFor: ["-"]' to make a step wait for all previous steps to succeed.

2. Step 2: Analyze options for correct workflow

   steps: - name: 'gcr.io/cloud-builders/docker' args: ['build', '-t', 'gcr.io/my-project/my-image', '.'] - name: 'gcr.io/cloud-builders/docker' args: ['run', 'my-image', 'test'] waitFor: ['-'] - name: 'gcr.io/cloud-builders/gcloud' args: ['app', 'deploy'] waitFor: ['-'] in steps: - name: 'gcr.io/cloud-builders/docker' args: ['build', '-t', 'gcr.io/my-project/my-image', '.'] - name: 'gcr.io/cloud-builders/docker' args: ['run', 'my-image', 'test'] waitFor: ['-'] - name: 'gcr.io/cloud-builders/gcloud' args: ['app', 'deploy'] waitFor: ['-'] ensures tests wait for build, and deploy waits for both.

3. Final Answer:

   steps: - name: 'gcr.io/cloud-builders/docker' args: ['build', '-t', 'gcr.io/my-project/my-image', '.'] - name: 'gcr.io/cloud-builders/docker' args: ['run', 'my-image', 'test'] waitFor: ['-'] - name: 'gcr.io/cloud-builders/gcloud' args: ['app', 'deploy'] waitFor: ['-'] -> Option A

4. Quick Check:

   waitFor ['-'] on test and deploy enforces build -> test -> deploy [OK]

Hint: Use waitFor: ['-'] on test and deploy steps for sequential workflow [OK]

Common Mistakes:

• Adding 'waitFor' incorrectly on all steps
• Omitting 'waitFor' causing deploy to run too early
• Misplacing 'waitFor' inside wrong steps