.TH "GCLOUD_BUILDS_TRIGGERS_UPDATE_BITBUCKETSERVER" 1



.SH "NAME"
.HP
gcloud builds triggers update bitbucketserver \- updates Bitbucket Server trigger used by Cloud Build



.SH "SYNOPSIS"
.HP
\f5gcloud builds triggers update bitbucketserver\fR (\fITRIGGER\fR\ :\ \fB\-\-region\fR=\fIREGION\fR) (\fB\-\-trigger\-config\fR=\fIPATH\fR\ |\ \fB\-\-bitbucket\-server\-config\-resource\fR=\fIBITBUCKET_SERVER_CONFIG_RESOURCE\fR\ \fB\-\-description\fR=\fIDESCRIPTION\fR\ \fB\-\-ignored\-files\fR=[\fIGLOB\fR,...]\ \fB\-\-included\-files\fR=[\fIGLOB\fR,...]\ \fB\-\-project\-key\fR=\fIPROJECT_KEY\fR\ \fB\-\-repo\-slug\fR=\fIREPO_SLUG\fR\ \fB\-\-[no\-]require\-approval\fR\ \fB\-\-service\-account\fR=\fISERVICE_ACCOUNT\fR\ \fB\-\-branch\-pattern\fR=\fIREGEX\fR\ |\ \fB\-\-tag\-pattern\fR=\fIREGEX\fR\ |\ \fB\-\-comment\-control\fR=\fICOMMENT_CONTROL\fR;\ default=\f5"COMMENTS_ENABLED"\fR\ \fB\-\-pull\-request\-pattern\fR=\fIREGEX\fR\ \fB\-\-build\-config\fR=\fIPATH\fR\ |\ \fB\-\-inline\-config\fR=\fIPATH\fR\ |\ [\fB\-\-dockerfile\fR=\fIDOCKERFILE\fR\ \fB\-\-dockerfile\-image\fR=\fIDOCKERFILE_IMAGE\fR\ :\ \fB\-\-dockerfile\-dir\fR=\fIDOCKERFILE_DIR\fR]\ \fB\-\-clear\-substitutions\fR\ |\ \fB\-\-remove\-substitutions\fR=[\fIKEY\fR,...]\ |\ \fB\-\-update\-substitutions\fR=[\fIKEY\fR=\fIVALUE\fR,...]) [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Updates Bitbucket Server trigger used by Cloud Build.



.SH "EXAMPLES"

To update the branch pattern of the trigger:

.RS 2m
$ gcloud builds triggers update bitbucketserver my\-trigger \e
    \-\-branch\-pattern=".*"
.RE

To update the build config of the trigger:

.RS 2m
$ gcloud builds triggers update bitbucketserver my\-trigger \e
    \-\-build\-config="cloudbuild.yaml"
.RE

To update the substitutions of the trigger:.RS 2m
$ gcloud builds triggers update bitbucketserver my\-trigger \e
    \-\-update\-substitutions=_REPO_NAME=my\-repo,_BRANCH_NAME=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 "REQUIRED FLAGS"

.RS 2m
.TP 2m

Exactly one of these must be specified:


.RS 2m
.TP 2m
\fB\-\-trigger\-config\fR=\fIPATH\fR

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

.TP 2m

Flag based trigger configuration


.RS 2m
.TP 2m
\fB\-\-bitbucket\-server\-config\-resource\fR=\fIBITBUCKET_SERVER_CONFIG_RESOURCE\fR

Bitbucket Server config resource name.

.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

Build trigger description.

.TP 2m
\fB\-\-ignored\-files\fR=[\fIGLOB\fR,...]

Glob filter. Changes only affecting ignored files won't trigger builds.

.TP 2m
\fB\-\-included\-files\fR=[\fIGLOB\fR,...]

Glob filter. Changes affecting at least one included file will trigger builds.

.TP 2m
\fB\-\-project\-key\fR=\fIPROJECT_KEY\fR

Bitbucket Server project key.

.TP 2m
\fB\-\-repo\-slug\fR=\fIREPO_SLUG\fR

Bitbucket Server repository slug.

.TP 2m
\fB\-\-[no\-]require\-approval\fR

Require manual approval for triggered builds. Use \fB\-\-require\-approval\fR to
enable and \fB\-\-no\-require\-approval\fR to disable.

.TP 2m
\fB\-\-service\-account\fR=\fISERVICE_ACCOUNT\fR

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:
\f5projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}\fR.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-branch\-pattern\fR=\fIREGEX\fR

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.

.TP 2m
\fB\-\-tag\-pattern\fR=\fIREGEX\fR

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.

.TP 2m

Pull Request settings


.RS 2m
.TP 2m
\fB\-\-comment\-control\fR=\fICOMMENT_CONTROL\fR; default=\f5"COMMENTS_ENABLED"\fR

Require a repository collaborator or owner to comment '/gcbrun' on a pull
request before running the build. \fICOMMENT_CONTROL\fR must be one of:

.RS 2m
.TP 2m
\fBCOMMENTS_DISABLED\fR
Do not require comments on Pull Requests before builds are triggered.
.TP 2m
\fBCOMMENTS_ENABLED\fR
Enforce that repository owners or collaborators must comment on Pull Requests
before builds are triggered.
.TP 2m
\fBCOMMENTS_ENABLED_FOR_EXTERNAL_CONTRIBUTORS_ONLY\fR
Enforce that repository owners or collaborators must comment on external
contributors' Pull Requests before builds are triggered.
.RE
.sp


.TP 2m
\fB\-\-pull\-request\-pattern\fR=\fIREGEX\fR

A regular expression specifying which base git branch to match for pull request
events.

This pattern is used as a regular expression 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.

.RE
.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-build\-config\fR=\fIPATH\fR

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

.TP 2m
\fB\-\-inline\-config\fR=\fIPATH\fR

Local path to a YAML or JSON file containing a build configuration.

.TP 2m

Dockerfile build configuration flags


.RS 2m
.TP 2m
\fB\-\-dockerfile\fR=\fIDOCKERFILE\fR

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.

.TP 2m
\fB\-\-dockerfile\-image\fR=\fIDOCKERFILE_IMAGE\fR

Docker image name to build.

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

.TP 2m
\fB\-\-dockerfile\-dir\fR=\fIDOCKERFILE_DIR\fR

Location of the directory containing the Dockerfile in the repository.

The directory will also be used as the Docker build context.

.RE
.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-substitutions\fR

Clear existing substitutions.

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

Remove existing substitutions if present.

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

Update or add to existing substitutions. Substitutions are parameters to be
substituted or add in the build specification.

For example (using some nonsensical substitution keys; all keys must begin with
an underscore):

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

This will add the provided substitutions to the existing substitutions and
results 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".

Only the following built\-in variables can be specified with the
\f5\-\-substitutions\fR flag: REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID,
COMMIT_SHA, SHORT_SHA.

For more details, see:
https://cloud.google.com/build/docs/build\-config\-file\-schema#substitutions


.RE
.RE
.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"

These variants are also available:

.RS 2m
$ gcloud alpha builds triggers update bitbucketserver
.RE

.RS 2m
$ gcloud beta builds triggers update bitbucketserver
.RE