Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to manually deploy your application to a specific target.
During normal use, Cloud Deploy deploys your application into each
target in the progression, in sequence.
But you can also manually deploy your application to any defined target.
You can manually deploy a new or an existing release.
Manually deploy an existing release
If a release is already created, you can simply promote it to the intended
target:
RELEASE_NAME is the name of the release which you're
manually promoting to the intended target.
PIPELINE_NAME is the name of the delivery pipeline that
describes the automated deployment progression you're overriding.
TARGET_NAME is the name of the target you're manually
deploying to.
REGION is the name of the region in which the release
was created, for example us-central1. This is required.
Manually deploy a new release
By default, when you create a release Cloud Deploy automatically
deploys it to the first target in the promotion sequence. But you can specify a
target other than the first one.
As with the default first target in the progression, Cloud Deploy
automatically creates the rollout for the specified target and deploys the
release there.
To manually deploy a new release, run the following command:
RELEASE_NAME is the name of the release which you're
manually promoting to the intended target.
PIPELINE_NAME is the name of the delivery pipeline that
describes the automated deployment progression you're overriding.
TARGET_NAME is the name of the target you're manually
deploying to.
REGION is the name of the region in which to create the
release, for example us-central1. This is required.
Effect of manual deployment on the progression
When you manually deploy to a specific target and then promote the release
without specifying a target, Cloud Deploy promotes it to the correct
next target in the progression. This is because the service tracks the furthest
target to which a release has been deployed. If the release is already in the
last target in the progression, Cloud Deploy returns a message
indicating there is no further target to promote to.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 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."]]