Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan cara men-deploy aplikasi secara manual ke target tertentu.
Selama penggunaan normal, Cloud Deploy men-deploy aplikasi Anda ke setiap target dalam progres, secara berurutan.
Namun, Anda juga dapat men-deploy aplikasi secara manual ke target yang ditentukan.
Anda dapat men-deploy rilis baru atau yang sudah ada secara manual.
Men-deploy rilis yang ada secara manual
Jika rilis sudah dibuat, Anda cukup mempromosikannya ke target
yang diinginkan:
RELEASE_NAME adalah nama rilis yang Anda promosikan secara manual ke target yang diinginkan.
PIPELINE_NAME adalah nama pipeline pengiriman yang
menjelaskan progres deployment otomatis yang Anda ganti.
TARGET_NAME adalah nama target tempat Anda men-deploy secara manual.
REGION adalah nama region tempat rilis
dibuat, misalnya us-central1. Wajib diisi.
Men-deploy rilis baru secara manual
Secara default, saat Anda membuat rilis, Cloud Deploy akan otomatis men-deploynya ke target pertama dalam urutan promosi. Namun, Anda dapat menentukan
target selain yang pertama.
Seperti target pertama default dalam progres, Cloud Deploy akan otomatis membuat rollout untuk target yang ditentukan dan men-deploy rilis di sana.
Untuk men-deploy rilis baru secara manual, jalankan perintah berikut:
RELEASE_NAME adalah nama rilis yang Anda promosikan secara manual ke target yang diinginkan.
PIPELINE_NAME adalah nama pipeline pengiriman yang
menjelaskan progres deployment otomatis yang Anda ganti.
TARGET_NAME adalah nama target tempat Anda men-deploy secara manual.
REGION adalah nama region tempat rilis akan dibuat, misalnya us-central1. Wajib diisi.
Dampak deployment manual terhadap progres
Saat Anda men-deploy ke target tertentu secara manual, lalu mempromosikan rilis tanpa menentukan target, Cloud Deploy akan mempromosikannya ke target berikutnya yang benar dalam progres. Hal ini karena layanan melacak target
terjauh tempat rilis telah di-deploy. Jika rilis sudah berada di target terakhir dalam progres, Cloud Deploy akan menampilkan pesan yang menunjukkan bahwa tidak ada target lebih lanjut untuk dipromosikan.
[[["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-09-03 UTC."],[[["\u003cp\u003eThis page details the process of manually deploying an application to a specific target using Cloud Deploy, overriding the automated deployment progression.\u003c/p\u003e\n"],["\u003cp\u003eYou can manually deploy an existing release to a target using the \u003ccode\u003egcloud deploy releases promote\u003c/code\u003e command, specifying the release, pipeline, target, and region.\u003c/p\u003e\n"],["\u003cp\u003eA new release can also be manually deployed to a target other than the first one in the sequence, and the \u003ccode\u003egcloud deploy releases create\u003c/code\u003e command allows for the creation and deployment of a release to a specified target.\u003c/p\u003e\n"],["\u003cp\u003eWhen a manual deployment is done, Cloud Deploy keeps track of the furthest target the release has reached and will continue the automated sequence from there when asked to.\u003c/p\u003e\n"]]],[],null,["# Deploy manually\n\nThis page describes how to manually deploy your application to a specific target.\n\nDuring normal use, Cloud Deploy deploys your application into each\ntarget in the [progression](/deploy/docs/terminology#progression), in sequence.\nBut you can also manually deploy your application to any defined target.\n\nYou can manually deploy a new or an existing release.\n\nManually deploy an existing release\n-----------------------------------\n\nIf a release is already created, you can simply promote it to the intended\ntarget: \n\n gcloud deploy releases promote --release=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eRELEASE_NAME\u003c/span\u003e\u003c/var\u003e \\\n --delivery-pipeline=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePIPELINE_NAME\u003c/span\u003e\u003c/var\u003e \\\n --to-target=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eTARGET_NAME\u003c/span\u003e\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003eRELEASE_NAME\u003c/var\u003e is the name of the release which you're\n manually promoting to the intended target.\n\n- \u003cvar translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e is the name of the delivery pipeline that\n describes the automated deployment progression you're overriding.\n\n- \u003cvar translate=\"no\"\u003eTARGET_NAME\u003c/var\u003e is the name of the target you're manually\n deploying to.\n\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is the name of the region in which the release\n was created, for example `us-central1`. This is required.\n\nManually deploy a new release\n-----------------------------\n\nBy default, when you create a release Cloud Deploy automatically\ndeploys it to the first target in the promotion sequence. But you can specify a\ntarget other than the first one.\n\nAs with the default first target in the progression, Cloud Deploy\nautomatically creates the `rollout` for the specified target and deploys the\nrelease there.\n\nTo manually deploy a new release, run the following command: \n\n gcloud deploy releases create \\\n --release=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eRELEASE_NAME\u003c/span\u003e\u003c/var\u003e \\\n --delivery-pipeline=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePIPELINE_NAME\u003c/span\u003e\u003c/var\u003e \\\n --to-target=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eTARGET_NAME\u003c/span\u003e\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eREGION\u003c/span\u003e\u003c/var\u003e\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003eRELEASE_NAME\u003c/var\u003e is the name of the release which you're\n manually promoting to the intended target.\n\n- \u003cvar translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e is the name of the delivery pipeline that\n describes the automated deployment progression you're overriding.\n\n- \u003cvar translate=\"no\"\u003eTARGET_NAME\u003c/var\u003e is the name of the target you're manually\n deploying to.\n\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e is the name of the region in which to create the\n release, for example `us-central1`. This is required.\n\nEffect of manual deployment on the progression\n----------------------------------------------\n\nWhen you manually deploy to a specific target and then promote the release\nwithout specifying a target, Cloud Deploy promotes it to the correct\nnext target in the progression. This is because the service tracks the furthest\ntarget to which a release has been deployed. If the release is already in the\nlast target in the progression, Cloud Deploy returns a message\nindicating there is no further target to promote to."]]
