HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/396/help/man/man1/gcloud_alpha_deploy_releases_abandon.1
.TH "GCLOUD_ALPHA_DEPLOY_RELEASES_ABANDON" 1



.SH "NAME"
.HP
gcloud alpha deploy releases abandon \- abandons a release



.SH "SYNOPSIS"
.HP
\f5gcloud alpha deploy releases abandon\fR (\fIRELEASE\fR\ :\ \fB\-\-delivery\-pipeline\fR=\fIDELIVERY_PIPELINE\fR\ \fB\-\-region\fR=\fIREGION\fR) [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR After a release is abandoned, no new rollouts can be created from
it.

Rollouts of abandoned releases can't be rolled back to.

Existing rollouts of abandoned releases will be unaffected.



.SH "EXAMPLES"

To abandon a release called \f5test\-release\fR for delivery pipeline
\f5test\-pipeline\fR in region \f5us\-central1\fR, run:

.RS 2m
$ gcloud alpha deploy releases abandon test\-release \e
    \-\-delivery\-pipeline=test\-pipeline \-\-region=us\-central1
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Release resource \- The name of the Release. The arguments in this group can be
used to specify the attributes of this resource. (NOTE) Some attributes are not
given arguments in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5release\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIRELEASE\fR

ID of the release or fully qualified identifier for the release.

To set the \f5release\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5release\fR on the command line.
.RE
.sp

This positional argument must be specified if any of the other arguments in this
group are specified.

.TP 2m
\fB\-\-delivery\-pipeline\fR=\fIDELIVERY_PIPELINE\fR

The delivery pipeline associated with the release. Alternatively, set the
property [deploy/delivery\-pipeline].

To set the \f5delivery\-pipeline\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5release\fR on the command line with a fully specified
name;
.IP "\(bu" 2m
provide the argument \f5\-\-delivery\-pipeline\fR on the command line;
.IP "\(bu" 2m
set the property \f5deploy/delivery_pipeline\fR.
.RE
.sp

.TP 2m
\fB\-\-region\fR=\fIREGION\fR

The Cloud region for the release. Alternatively, set the property
[deploy/region].

To set the \f5region\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5release\fR on the command line with a fully specified
name;
.IP "\(bu" 2m
provide the argument \f5\-\-region\fR on the command line;
.IP "\(bu" 2m
set the property \f5deploy/region\fR.
.RE
.sp


.RE
.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist. These variants are also available:

.RS 2m
$ gcloud deploy releases abandon
.RE

.RS 2m
$ gcloud beta deploy releases abandon
.RE