- NAME
-
- gcloud builds triggers import - import a build trigger
- SYNOPSIS
-
-
gcloud builds triggers import--source=PATH[--region=REGION] [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
- To import a trigger from a file: $ cat > trigger.yaml <<EOF name:
my-trigger github: owner: GoogleCloudPlatform name: cloud-builders push: branch:
.
EOF - EXAMPLES
- To import a build trigger from a file called trigger.yaml, run:
gcloud builds triggers import --source = trigger.yaml - REQUIRED FLAGS
-
-
--source=PATH - File path where trigger should be imported from.
-
- OPTIONAL FLAGS
-
-
--region=REGION - The region of the Cloud Build Service to use. Must be set to a supported region
name (e.g.
us-central1). If unset,builds/region, which is the default region to use when working with Cloud Build resources, is used. If builds/region is unset, region is set toglobal. Note: Region must be specified in 2nd gen repo;globalis not supported.
-
- 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 helpfor details. - NOTES
- These variants are also available:
gcloud alpha builds triggers importgcloud beta builds triggers import
gcloud builds triggers import
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 2026-05-27 UTC.
