- NAME
-
- gcloud beta builds triggers run - run a build trigger
- SYNOPSIS
-
-
gcloud beta builds triggers run
(TRIGGER
:--region
=REGION
) [--substitutions
=[KEY
=VALUE
,…]] [--branch
=BRANCH
|--sha
=SHA
|--tag
=TAG
] [GCLOUD_WIDE_FLAG …
]
-
- DESCRIPTION
-
(BETA)
Run a build trigger. - EXAMPLES
-
To run a build trigger, run:
gcloud beta builds triggers run MY-TRIGGER --branch=master
- POSITIONAL ARGUMENTS
-
-
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
project
attribute:-
provide the argument
TRIGGER
on the command line with a fully specified name; -
provide the argument
--project
on the command line; -
set the property
core/project
.
This must be specified.
TRIGGER
-
ID of the trigger or fully qualified identifier for the trigger.
To set the
trigger
attribute:-
provide the argument
TRIGGER
on the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
-
provide the argument
--region
=REGION
-
The Cloud location for the trigger.
To set the
region
attribute:-
provide the argument
TRIGGER
on the command line with a fully specified name; -
provide the argument
--region
on the command line; -
set the property
builds/region
.
-
provide the argument
-
provide the argument
-
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.
- FLAGS
-
--substitutions
=[KEY
=VALUE
,…]-
Parameters to be substituted in the build specification. For example:
gcloud beta builds triggers run … --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10
This will result in a build where every occurrence of
${_FAVORITE_COLOR}
in certain fields is replaced by "blue", and similarly for${_NUM_CANDIES}
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
-
At most one of these can be specified:
--branch
=BRANCH
- Branch to run.
--sha
=SHA
- SHA to run.
--tag
=TAG
- Tag to run.
- 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
$ gcloud help
for details. - NOTES
-
This command is currently in beta and might change without notice. These
variants are also available:
gcloud builds triggers run
gcloud alpha builds triggers run
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-02-06 UTC.