delivery pipeline

Related topics

• analysis job is part of delivery pipeline From the official documentation: “Your analysis job is configured as part of the delivery pipeline definition, inside a `strategy` stanza.”
• Automation is part of delivery pipeline From the official documentation: “All automations exist only within the scope of one delivery pipeline.”
• delivery pipeline is part of Cloud Deploy From the official documentation: “Delivery Pipeline being managed by Cloud Deploy.”
• delivery pipeline configures release From the official documentation: “The delivery pipeline defines the lifecycle of that release.”
• release is part of delivery pipeline From the official documentation: “If you have a delivery pipeline without any subresources (releases or rollouts), you can delete it by running the following command:”
• rollout is part of delivery pipeline From the official documentation: “If you have a delivery pipeline without any subresources (releases or rollouts), you can delete it by running the following command:”
• target is part of delivery pipeline From the official documentation: “If you change a delivery pipeline, or any of its targets, after a release is created, you can do the following:”
• Cloud Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
• Cloud Deploy works with Google Cloud Observability From the official documentation: “Google Cloud Observability collects and makes available logging data for Cloud Deploy.”
• 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 Deploy works with GKE From the official documentation: “Quickstart: Deploy an app to GKE by using Cloud Deploy”
• 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 Google Cloud Observability From the official documentation: “Cloud Run automatically uses Google Cloud Observability to aggregate and review your logs, as described in the [logging page](/run/docs/logging).”
• analysis job is part of Cloud Deploy From the official documentation: “By default, Cloud Deploy analysis can use many types of metrics from Google Cloud Observability.”
• analysis job works with Google Cloud Observability From the official documentation: “This section describes how to configure a Cloud Deploy analysis job for use with Google Cloud Observability.”
• Automation is part of Cloud Deploy From the official documentation: “Deletes a Cloud Deploy Automation.”
• Cloud Deploy works with GKE attached clusters From the official documentation: “This document describes how to configure and use canary deployments to deploy your applications to GKE or GKE attached clusters using Cloud Deploy with service-based networking.”
• Cloud Run works with target From the official documentation: “You now have a pipeline, with one multi-target comprising two GKE or Cloud Run targets, ready to deploy your application.”
• GKE works with Google Cloud Observability From the official documentation: “GKE is integrated with<br>Google Cloud Observability.”
• GKE works with target From the official documentation: “You now have a pipeline, with one multi-target comprising two GKE or Cloud Run targets, ready to deploy your application.”
• GKE attached clusters works with target From the official documentation: “The target can point to [GKE](/deploy/docs/config-files#for_gke_targets), [GKE attached clusters](/deploy/docs/config-files#for_anthos_targets), [Cloud Run](/deploy/docs/config-files#for_run_targets), or [custom targets](/deploy/docs/deploy-to-custom-targets).”
• release is part of Cloud Deploy From the official documentation: “Create and manage Release resources for Cloud Deploy.”
• rollout is part of Cloud Deploy From the official documentation: “Create and manage Rollout resources for Cloud Deploy.”
• rollout is part of release From the official documentation: “You can view a list of rollouts for this release, and click a rollout to [view rollout details](#viewing_rollouts).”
• rollout depends on release From the official documentation: “When you roll back a target, Cloud Deploy creates a new `rollout` resource based on a previous release.”
• target is part of Cloud Deploy From the official documentation: “Create and manage Target resources for Cloud Deploy.”