.TH "GCLOUD_ALPHA_BUILDS_TRIGGERS_RUN" 1



.SH "NAME"
.HP
gcloud alpha builds triggers run \- run a build trigger



.SH "SYNOPSIS"
.HP
\f5gcloud alpha builds triggers run\fR (\fITRIGGER\fR\ :\ \fB\-\-region\fR=\fIREGION\fR) [\fB\-\-substitutions\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-branch\fR=\fIBRANCH\fR\ |\ \fB\-\-sha\fR=\fISHA\fR\ |\ \fB\-\-tag\fR=\fITAG\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Run a build trigger.



.SH "EXAMPLES"

To run a build trigger, run:

.RS 2m
$ gcloud alpha builds triggers run MY\-TRIGGER \-\-branch=master
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Trigger resource \- Build Trigger. 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 \f5TRIGGER\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
\fITRIGGER\fR

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

To set the \f5trigger\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5TRIGGER\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\-\-region\fR=\fIREGION\fR

The Cloud location for the trigger.

To set the \f5region\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5TRIGGER\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 \f5builds/region\fR.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-substitutions\fR=[\fIKEY\fR=\fIVALUE\fR,...]

Parameters to be substituted in the build specification. For example:

.RS 2m
$ gcloud alpha builds triggers run ... \e
    \-\-substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10
.RE

This will result in a build where every occurrence of \f5${_FAVORITE_COLOR}\fR
in certain fields is replaced by "blue", and similarly for \f5${_NUM_CANDIES}\fR
and "10".

Substitutions can be applied to user\-defined variables (starting with an
underscore) and to the following built\-in variables: REPO_NAME, BRANCH_NAME,
TAG_NAME, REVISION_ID, COMMIT_SHA, SHORT_SHA.

For more details, see:
https://cloud.google.com/build/docs/configuring\-builds/substitute\-variable\-values

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-branch\fR=\fIBRANCH\fR

Branch to run.

.TP 2m
\fB\-\-sha\fR=\fISHA\fR

SHA to run.

.TP 2m
\fB\-\-tag\fR=\fITAG\fR

Tag to run.


.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 builds triggers run
.RE

.RS 2m
$ gcloud beta builds triggers run
.RE