Adalah nama file konfigurasi pipeline pengiriman, biasanya
clouddeploy.yaml. Wajib diisi.
REGION
Adalah nama region tempat pipeline pengiriman dibuat, misalnya
us-central1. Wajib diisi.
PROJECT_ID
Adalah project ID dari project tempat pipeline pengiriman
dibuat. Wajib diisi.
Pipeline pengiriman kini dalam status ditangguhkan, yang mencegah pembuatan, promosi, rollback, dan deployment ulang rilis, serta persetujuan peluncuran.
Peluncuran dari pipeline pengiriman yang ditangguhkan
Jika ada peluncuran yang sedang berlangsung atau diantrekan saat Anda menangguhkan pipeline
pengiriman, peluncuran tersebut akan dilanjutkan hingga selesai—peluncuran tersebut tidak
dibatalkan. Namun, karena Anda tidak dapat membuat atau mempromosikan rilis, tidak ada peluncuran
baru yang dapat dibuat menggunakan pipeline tersebut hingga dilanjutkan.
Izin IAM yang diperlukan untuk menangguhkan pipeline
Izin IAM yang diperlukan untuk menangguhkan pipeline pengiriman
disertakan dalam peran berikut:
roles/clouddeploy.admin
roles/clouddeploy.operator
roles/clouddeploy.developer
Melanjutkan pipeline pengiriman yang ditangguhkan
Untuk mengaktifkan kembali pipeline pengiriman yang ditangguhkan:
Dalam file konfigurasi pipeline pengiriman, hapus properti
suspended: true, atau tetapkan ke false.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-17 UTC."],[[["\u003cp\u003eSuspending a Cloud Deploy delivery pipeline prevents actions such as creating, promoting, rolling back, or redeploying releases, as well as approving or rejecting rollouts.\u003c/p\u003e\n"],["\u003cp\u003eA delivery pipeline can be suspended by including the \u003ccode\u003esuspended: true\u003c/code\u003e property in the pipeline's configuration file, typically \u003ccode\u003eclouddeploy.yaml\u003c/code\u003e, at the top level.\u003c/p\u003e\n"],["\u003cp\u003eRollouts already in progress will complete even after the pipeline is suspended, but no new rollouts can be created.\u003c/p\u003e\n"],["\u003cp\u003eTo resume a suspended delivery pipeline, remove the \u003ccode\u003esuspended: true\u003c/code\u003e property or set it to \u003ccode\u003efalse\u003c/code\u003e in the configuration file and then apply the configuration.\u003c/p\u003e\n"],["\u003cp\u003eSuspended pipelines are identified by a lock icon in the Google Cloud console's Delivery pipelines view.\u003c/p\u003e\n"]]],[],null,["# Suspend a delivery pipeline\n\nThis page describes how to suspend a Cloud Deploy delivery pipeline.\n\nYou can *suspend* a delivery pipeline. Suspending a pipeline means that it can\nno longer be used for the following:\n\n- Create a release\n\n- Promote a release\n\n- Roll back a release\n\n- Redeploy a release\n\n- Approve or reject a rollout\n\nHere are some possible reasons for suspending a delivery pipeline:\n\n- There's a problem with a release and you want to prevent further action on\n that pipeline until the problem is found.\n\n- Your organization observes a holiday freeze, for example during peak holiday\n shopping season.\n\nTo suspend a delivery pipeline:\n\n1. In the delivery pipeline configuration file, include the following property:\n\n suspended: true\n\n This property goes at the top level, as shown: \n\n apiVersion: deploy.cloud.google.com/v1\n kind: DeliveryPipeline\n metadata:\n Name: my-app\n description: main application pipeline\n suspended: true\n serialPipeline:\n stages:\n - targetId: dev\n profiles: []\n - targetId: staging\n profiles: []\n - targetId: prod\n profiles: []\n\n2. Register the delivery pipeline:\n\n gcloud deploy apply --file=\u003cvar label=\"pipeline\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePIPELINE_CONFIG\u003c/span\u003e\u003c/var\u003e --region=\u003cvar label=\"region\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e --project=\u003cvar label=\"project id\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e\n\n Where:\n - \u003cvar translate=\"no\"\u003ePIPELINE_CONFIG\u003c/var\u003e\n\n Is the name of the delivery pipeline configuration file, typically\n `clouddeploy.yaml`. This is required.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\n Is the name of the region in which the delivery pipeline was created, for\n example `us-central1`. This is required.\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n Is the project ID of the project in which the delivery pipeline was\n created. This is required.\n\nThe delivery pipeline is now in a suspended state, which prevents release\ncreation, promotion, rollback and redeploy, and rollout approval.\n\nRollouts from suspended delivery pipelines\n------------------------------------------\n\nIf there are any rollouts in progress or queued when you suspend a delivery\npipeline, those rollouts continue to completion---they are not\ncanceled. However, because you can't create or promote a release, no new\nrollouts can be created using that pipeline until it's [resumed](#resume_a_suspended_delivery_pipeline).\n\nIAM permissions required for suspending a pipeline\n--------------------------------------------------\n\nThe IAM permissions required for suspending a delivery pipeline\nare included in the following roles:\n\n- roles/clouddeploy.admin\n\n- roles/clouddeploy.operator\n\n- roles/clouddeploy.developer\n\nResume a suspended delivery pipeline\n------------------------------------\n\nTo re-enable a suspended delivery pipeline:\n\n1. In the delivery pipeline configuration file, remove the property\n `suspended: true`, or set it to `false`.\n\n2. Apply the configuration:\n\n gcloud deploy apply --file=\u003cvar label=\"pipeline\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePIPELINE_CONFIG\u003c/span\u003e\u003c/var\u003e --region=\u003cvar label=\"region\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e --project=\u003cvar label=\"project id\" translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePROJECT_ID\u003c/span\u003e\u003c/var\u003e\n\nFind out what pipelines are suspended\n-------------------------------------\n\nAny delivery pipelines that are locked are shown with a lock icon next to the\nname in the Google Cloud console **Delivery pipelines** view:\n\nWhat's next\n-----------\n\n- Find out how to [view a delivery pipeline](/deploy/docs/view-pipeline)\n that's already in use.\n\n- Learn how to [update a delivery pipeline](/deploy/docs/update-pipeline).\n\n- Find out how to [delete a delivery pipeline](/deploy/docs/delete-pipeline).\n\n- Learn how to [use service notifications](/deploy/docs/subscribe-deploy-notifications)"]]