Adalah nama rilis yang akan ditinggalkan. Wajib diisi.
PIPELINE_NAME
Adalah nama pipeline pengiriman yang membuat rilis. Hal ini
wajib.
REGION
Adalah nama region tempat rilis dibuat, misalnya
us-central1. Wajib diisi.
Izin IAM
Izin IAM yang diperlukan untuk membatalkan rilis
disertakan dalam peran berikut:
roles/clouddeploy.admin
roles/clouddeploy.operator
roles/clouddeploy.developer
Peluncuran dari rilis yang ditinggalkan
Jika Anda membatalkan rilis, peluncuran apa pun yang dibuat dari rilis tersebut yang sedang
berlangsung atau diantrekan akan dilanjutkan hingga selesai—peluncuran tersebut tidak dibatalkan. Namun, Anda
tidak dapat membuat peluncuran baru dari rilis yang ditinggalkan.
Melihat rilis yang ditinggalkan
Di konsol Google Cloud , Anda dapat melihat apakah rilis telah dihentikan. Tab
Rilis, di halaman detail Pipeline pengiriman, memberi label rilis sebagai
"ditinggalkan":
[[["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\u003eThis page details the process of permanently abandoning a Cloud Deploy release, which is irreversible and prevents promotion or rollback to that release.\u003c/p\u003e\n"],["\u003cp\u003eReleases are abandoned due to issues like bugs, security concerns, or deprecated features, effectively deactivating them from further use.\u003c/p\u003e\n"],["\u003cp\u003eTo abandon a release, use the \u003ccode\u003egcloud deploy releases abandon\u003c/code\u003e command, specifying the release name, delivery pipeline, and region.\u003c/p\u003e\n"],["\u003cp\u003eAbandoning a release does not cancel rollouts that are already in progress, but it does prevent the creation of new rollouts from the abandoned release.\u003c/p\u003e\n"],["\u003cp\u003eAbandoned releases are labeled as such in the Google Cloud console's "Releases" tab, and specific IAM roles like \u003ccode\u003eclouddeploy.admin\u003c/code\u003e, \u003ccode\u003eclouddeploy.operator\u003c/code\u003e, and \u003ccode\u003eclouddeploy.developer\u003c/code\u003e are needed to abandon releases.\u003c/p\u003e\n"]]],[],null,["# Abandon a release\n\nThis page describes how to permanently abandon a Cloud Deploy\nrelease.\n\nYou can permanently [abandon](/deploy/docs/terminology#abandon) a release. An\nabandoned release has the following characteristics:\n\n- You can't promote an abandoned release.\n\n- You can't roll back to an abandoned release.\n\n- You can't unabandon a release. After you abandon a release, it's permanently\n deactivated.\n\nReasons for abandoning a release include the following, for example:\n\n- There's a bug in the release\n\n- There's a security issue in the release\n\n- A feature included in the release has been deprecated\n\nTo abandon a release, run the following command: \n\n gcloud deploy releases abandon \u003cvar translate=\"no\"\u003eRELEASE_NAME\u003c/var\u003e --delivery-pipeline=\u003cvar translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003eRELEASE_NAME\u003c/var\u003e\n\n Is the name of the release to abandon. This is required.\n- \u003cvar translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e\n\n Is the name of the delivery pipeline that created the release. This is\n required.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\n Is the name of the region in which the release was created, for example\n `us-central1`. This is required.\n\nIAM permissions\n---------------\n\nThe IAM permissions required for abandoning a release are\nincluded in the following roles:\n\n- roles/clouddeploy.admin\n\n- roles/clouddeploy.operator\n\n- roles/clouddeploy.developer\n\nRollouts from abandoned releases\n--------------------------------\n\nWhen you abandon a release, any rollouts created from that release that are in\nprogress or queued continue to completion---they are not cancelled. However, you\ncan't create new rollouts from an abandoned release.\n\nView abandoned releases\n-----------------------\n\nIn Google Cloud console, you can see if a release has been abandoned. The\n**Releases** tab, on the Delivery pipeline details page, labels the release as\n\"abandoned\":"]]
