CI/CD pipelines

Related topics

• Artifact Registry configures CI/CD pipelines From the official documentation: “[Cloud Build](/build/docs/overview) and [Artifact Registry](/artifact-registry/docs/overview) let you implement CI/CD pipelines to automate building, testing, and deployment of your ML models.”
• CI/CD pipelines works with Cloud Build From the official documentation: “To create and manage CI/CD pipelines for cloud applications, you can use tools like [Cloud Build](/build/docs/overview) and [Cloud Deploy](/deploy/docs).”
• CI/CD pipelines works with Cloud Deploy From the official documentation: “To create and manage CI/CD pipelines for cloud applications, you can use tools like [Cloud Build](/build/docs/overview) and [Cloud Deploy](/deploy/docs).”
• CI/CD pipelines works with Infrastructure as Code From the official documentation: “When combined with CI/CD pipelines and automation, IaC also gives you the ability to adopt practices such as *policy as code* with tools like OPA.”
• Cloud Build is part of CI/CD pipelines From the official documentation: “- Automate deployment with CI/CD pipelines. You can use [Cloud Build](/build/docs/overview) to build containers, version artifacts, and trigger deployment to Agent Platform endpoints.”
• Cloud Build configures CI/CD pipelines From the official documentation: “Use products like [Cloud Build](/build/docs/overview) and [Cloud Deploy](/deploy/docs/overview) to create and manage your CI/CD pipelines.”
• Cloud Deploy configures CI/CD pipelines From the official documentation: “Use products like [Cloud Build](/build/docs/overview) and [Cloud Deploy](/deploy/docs/overview) to create and manage your CI/CD pipelines.”
• Artifact Registry works with Cloud Build From the official documentation: “1. Builds your container and pushes it to Artifact Registry.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Cloud Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Artifact Registry works with Google Kubernetes Engine From the official documentation: “You can identify frequently pulled images and copy them to Artifact Registry for deployments to Google Cloud environments such as Google Kubernetes Engine or Cloud Run.”
• Cloud Build works with Cloud Deploy From the official documentation: “The pipeline uses Cloud Build for CI and Cloud Deploy for CD.”
• Cloud Deploy works with Cloud Storage From the official documentation: “Delete the Cloud Storage buckets that Cloud Deploy created.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Cloud Deploy works with GKE From the official documentation: “Quickstart: Deploy an app to GKE by using Cloud Deploy”
• Cloud Deploy works with Google Kubernetes Engine From the official documentation: “You might need to enable other APIs to use Cloud Deploy features, including Google Kubernetes Engine, Cloud Storage, and Cloud Build APIs.”
• Cloud Deploy depends on Pub/Sub From the official documentation: “Cloud Deploy uses Pub/Sub to publish notifications for two purposes:”
• Cloud Deploy works with Pub/Sub From the official documentation: “Cloud Deploy publishes operational messages to Pub/Sub.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Google Kubernetes Engine From the official documentation: “By default, GKE clusters send system log data and system metric data to Logging and Monitoring.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• Artifact Registry works with Cloud Logging From the official documentation: “Artifact Registry sends the following types of audit log data to Cloud Logging:”
• Artifact Registry secures Cloud Run From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Artifact Registry secures Google Kubernetes Engine From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry works with Pub/Sub From the official documentation: “When you activate the Artifact Registry API in a Google Cloud project, Artifact Registry tries to automatically create a Pub/Sub topic with the topic ID `gcr` using Google-owned and Google-managed encryption keys.”
• Cloud Build works with Cloud Logging From the official documentation: “- [`roles/logging.logWriter`](/iam/docs/roles-permissions/logging)— Required to store build logs in Cloud Logging.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build depends on GKE From the official documentation: “To deploy the application in your Kubernetes cluster, Cloud Build needs the Kubernetes Engine Developer [Identity and Access Management Role](/iam/docs/understanding-roles).”
• Cloud Build works with Google Kubernetes Engine From the official documentation: “This tutorial shows you how to validate configs with [Cloud Build](/build) when using Google Kubernetes Engine clusters.”
• Cloud Build works with Pub/Sub From the official documentation: “Cloud Build sends all build event updates, along with build metadata, [to Pub/Sub](/build/docs/subscribe-build-notifications) on either the `cloud-builds` topic or a user-defined topic.”
• Cloud Deploy depends on Cloud Build From the official documentation: “Cloud Deploy calls Cloud Build to render your manifests and to deploy to the target runtime.”
• Cloud Deploy works with Cloud Logging From the official documentation: “Cloud Deploy and its dependent services publish logs to Cloud Logging, part of Google Cloud Observability.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Run depends on Artifact Registry From the official documentation: “The containerized function is stored in Artifact Registry and deployed to Cloud Run as a service.”
• Cloud Run is an alternative to Google Kubernetes Engine From the official documentation: “**Agent and tool runtimes**: hosting and executing agents or MCP servers on runtimes such as Agent Runtime on Gemini Enterprise Agent Platform, Cloud Run, or Google Kubernetes Engine (GKE) incurs standard compute and runtime charges for those services.”
• Cloud Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• Cloud Storage works with Google Kubernetes Engine From the official documentation: “Often, media-related data residing in Cloud Storage is processed by applications running in Compute Engine or Google Kubernetes Engine, and the output of this process is written back to Cloud Storage.”
• GKE depends on Artifact Registry From the official documentation: “When you create or update a cluster, GKE pulls container images for the Kubernetes system software running on the control plane and nodes from Artifact Registry repositories in the `pkg.dev` or the `gcr.io` domain.”