Reviewing Test Results of Continuous Integration Pipeline
Start course

Google Cloud Platform (GCP) is a powerful platform that brings the flexibility and reliability of Google’s infrastructure to your projects. As a leader in AI, machine learning, and networking, GCP has a suite of tools and services for developers to use for almost any circumstance. Before using them, it’s good to learn the ins and outs of GCP and the most effective patterns for software development. The Professional Cloud Developer exam, as well as the industry at large, has been transformed by Continuous Integration (CI) and Continuous Deployment (CD), which enable developers to deliver code safely and securely into production once properly setup. This course will cover the Google best practices for setting up a CI/CD pipeline on GCP.

For support, queries or feedback relating to this course, please contact us at

Learning Objectives

  • Learn GCP core developer services
  • Create a CI/CD pipeline with Google Cloud Build
  • Test and deploy a containerized application

Intended Audience

Developers who are studying for the Google Cloud Professional Cloud Developer Certification exam.


To get the most out of this course, you should be fluent in at least one programming language and have some experience with Docker and Kubernetes.


Now that our pipeline has finished running, let's break down what happens while it runs. Reviewing the logs for each step can alert us to why certain failures occurred, as well as if something gets set incorrectly and passed along to another step in the pipeline. Since each step in the Cloud Build pipeline is run in a separate container, the logs for each step are isolated and easily retrievable, both from the CLI and the console.

Cloud Build also has a filter to allow easy browsing of builds based on status, tags, and several other identifiers. This can be extremely useful when needing to get a list of events based on specific criteria. These filters can be combined and customized to allow us to create reports and lists no matter how many events your organization may be running on a daily basis. Let's take a look at how we can put some of this into practice by using the console and the gcloud CLI to review and filter Cloud Build logs.

About the Author

Chris Blackden started his first IT job at the age of fifteen and has been doing it ever since. He’s held roles from Hardware Technician to Senior Software Engineer, and is currently working as a DevOps Engineer in a healthcare research organization. Some of his passions outside of work include cooking and eating spicy food, and old-school kung fu movies.