- NAME
-
- gcloud builds triggers create bitbucket-cloud - create a build trigger for a 2nd-gen Bitbucket Cloud repository
- SYNOPSIS
-
-
gcloud builds triggers create bitbucket-cloud(--trigger-config=PATH| [(--branch-pattern=REGEX|--tag-pattern=REGEX| [--pull-request-pattern=REGEX:--comment-control=COMMENT_CONTROL; default="COMMENTS_ENABLED"]) (--build-config=PATH|--inline-config=PATH| [--dockerfile=DOCKERFILE--dockerfile-image=DOCKERFILE_IMAGE:--dockerfile-dir=DOCKERFILE_DIR; default="/"]) :--description=DESCRIPTION--ignored-files=[GLOB,…]--included-files=[GLOB,…]--name=NAME--region=REGION--repository=REPOSITORY--[no-]require-approval--service-account=SERVICE_ACCOUNT--substitutions=[KEY=VALUE,…]]) [GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
- Create a build trigger for a 2nd-gen Bitbucket Cloud repository.
- EXAMPLES
-
To create a push trigger with a 2nd-gen repository for all branches:
gcloud builds triggers create bitbucket-cloud --name="my-trigger" --service-account="projects/my-project/serviceAccounts/my-byosa@my-project.iam.gserviceaccount.com" --repository="projects/1234/locations/us-central1/connections/myconn/repositories/myrepo" --branch-pattern=".*" --build-config="cloudbuild.yaml" --region=us-central1To create a pull request trigger with a 2nd-gen repository for main:
gcloud builds triggers create bitbucket-cloud --name="my-trigger" --service-account="projects/my-project/serviceAccounts/my-byosa@my-project.iam.gserviceaccount.com" --repository="projects/1234/locations/us-central1/connections/myconn/repositories/myrepo" --build-config="cloudbuild.yaml" --pull-request-pattern="^main$" --region=us-central1 - REQUIRED FLAGS
-
-
Exactly one of these must be specified:
--trigger-config=PATH- Path to Build Trigger config file (JSON or YAML format). For more details, see https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger
-
Flag based trigger configuration
--description=DESCRIPTION- Build trigger description.
--ignored-files=[GLOB,…]- Glob filter. Changes only affecting ignored files won't trigger builds.
--included-files=[GLOB,…]- Glob filter. Changes affecting at least one included file will trigger builds.
--name=NAME- Build trigger name.
--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. --repository=REPOSITORY-
Repository resource (2nd gen) to use, in the format
"projects/*/locations/*/connections/*/repositories/
". - --[no-]require-approval
-
Require manual approval for triggered builds. Use
--require-approval
to enable and--no-require-approvalto disable. - --service-account
=SERVICE_ACCOUNT -
The service account used for all user-controlled operations including
UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and CancelBuild. If no service
account is set, then the standard Cloud Build service account
([PROJECT_NUM]@system.gserviceaccount.com) is used instead. Format:
projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - --substitutions
=[KEY=VALUE,…] -
Parameters to be substituted in the build specification. For example:
gcloud builds triggers create bitbucket-cloud … --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10This 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
-
Exactly one of these must be specified:
- --branch-pattern
=REGEX -
A regular expression specifying which git branches to match.
This pattern is used as a regular expression search for any incoming pushes. For example, --branch-pattern=foo will match "foo", "foobar", and "barfoo". Events on a branch that does not match will be ignored.
The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax.
- --tag-pattern
=REGEX -
A regular expression specifying which git tags to match.
This pattern is used as a regular expression search for any incoming pushes. For example, --tag-pattern=foo will match "foo", "foobar", and "barfoo". Events on a tag that does not match will be ignored.
The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax.
-
Pull Request settings
- --pull-request-pattern
=REGEX -
Regular expression specifying which base git branch to match for pull request
events.
This pattern is used as a regex search for the base branch (the branch you are trying to merge into) for pull request updates. For example, --pull-request-pattern=foo will match "foo", "foobar", and "barfoo".
The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at https://github.com/google/re2/wiki/Syntax.
This flag argument must be specified if any of the other arguments in this group are specified.
- --comment-control
=COMMENT_CONTROL; default="COMMENTS_ENABLED" -
Require a repository collaborator or owner to comment '/gcbrun' on a pull
request before running the build.
COMMENT_CONTROLmust be one of:- COMMENTS_DISABLED
- Do not require comments on Pull Requests before builds are triggered.
- COMMENTS_ENABLED
- Enforce that repository owners or collaborators must comment on Pull Requests before builds are triggered.
- COMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY
- Enforce that repository owners or collaborators must comment on external contributors' Pull Requests before builds are triggered.
- COMMENTS_DISABLED
- --pull-request-pattern
- --branch-pattern
-
Exactly one of these must be specified:
- --build-config
=PATH -
Path to a YAML or JSON file containing the build configuration in the
repository.
For more details, see: https://cloud.google.com/cloud-build/docs/build-config
- --inline-config
=PATH - Local path to a YAML or JSON file containing a build configuration.
-
Dockerfile build configuration flags
- --dockerfile
=DOCKERFILE -
Path of Dockerfile to use for builds in the repository.
If specified, a build config will be generated to run docker build using the specified file.
The filename is relative to the Dockerfile directory.
This flag argument must be specified if any of the other arguments in this group are specified.
- --dockerfile-image
=DOCKERFILE_IMAGE -
Docker image name to build.
This flag argument must be specified if any of the other arguments in this group are specified.
- --dockerfile-dir
=DOCKERFILE_DIR; default="/" -
Location of the directory containing the Dockerfile in the repository.
The directory will also be used as the Docker build context.
- --dockerfile
- --build-config
-
Exactly one of these must be specified:
- 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 create bitbucket-cloudgcloud beta builds triggers create bitbucket-cloud
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-03-12 UTC.