Theclone property provides options for controlling how your repository is cloned by Bitbucket Pipelines during a build.

The following options are available for controlling the git clone behavior for the whole pipeline:

• lfs — support for Git LFS.

• depth — the depth of the Git clone.

• enabled — allows the Git clone to be disabled.

Additionally, theskip-ssl-verify option is available when theclone property is applied to an individualstep when the step is run on a self-hosted pipeline runner.

Property —clone

Required — No

Data type — Block of new-line separated key-value pairs (YAML spec - Block Mapping)

Allowed parent properties —step or the YAML root (clone can be a top-level property)

Allowed child properties — Requires one or more of thelfs,depth, andenabled properties.skip-ssl-verify is allowed when theclone element is in astep.

Example — using clone and enabled to only allow Git clone on selected steps

Example — using clone to configure global git clone behavior for a pipeline

Example — using clone to customize git clone behavior on a single step

Defines the depth of Git clones for all pipelines or a pipeline step. Usefull for a full clone. If not specified, the default is the last 50 commits. For information on the Git clone depth option, visitGit Documentation — git clone.

Property —depth

Required — No

Data type — Integer or String

Allowed values —full (for full depth) or any positive integer

Default value —50

Allowed parent properties —clone

Example — using the depth option to only clone the last two commits for every step in the pipeline

Example — using the depth option to only clone the last two commits for a single step

Thecloneenabled option is used to disable the git clone operation which is run at the start of every step. Theenabled option can be used to disable Git clone operations for a singlestep, or for all steps.

Property —enabled

Required — No

Data type — Boolean

Allowed values —true orfalse

Default value —true

Allowed parent properties —clone

Example — using the clone enabled option to disable git clone for all steps

Example — using the clone enabled option to disable git clone on a pipeline step

Thelfs options instructs git to download all LFS files for the repository during git clone operations. Whenlfs is set totrue as a global option, all LFS files will be downloaded at the start of every step. Whenlfs is set totrue on an individual step, then all the LFS files will be downloaded for that step. We recommend using LFS on individual steps or to download only the required files for each step to reduce build times and resource usage.

Property —lfs

Required — No

Data type — Boolean

Allowed values —true orfalse

Default value —false

Allowed parent properties —clone

Example — using LFS to download all LFS files in every step

Example — using lfs to selectively download LFS files

Theskip-ssl-verify option disables SSL verification during git clone, allowing the use of self-signed certificates.

Property —skip-ssl-verify

Required — No

Data type — Boolean

Allowed values —true orfalse

Default value —false

Allowed parent properties —clone (whenclone is set in astep)

Example — using skip-ssl-verify to disable SSL verification on git clone operations