Pipeline depth specification in YAML file seems to be ignored

James Hume_ezrukh

Hi,

I am trying to get the BitBucket pipeline to shallow clone my repository. My file looks like this:

 

image:
   <snip>

clone:
   depth: 1

pipelines:
   <snip>

 When I look at the pipeline build log, the git clone command does not include "--depth 1". Have I got the YAML layout above wrong?

Daniel Santos_157bm4

Hi @James Hume,

I believe you are facing some edge case or bug.
I was not able to reproduce this scenario.

When I browse the pipelines logs I see this in the first part of it:

Build setup (section)

+ umask 000
+ GIT_LFS_SKIP_SMUDGE=1 git clone --branch="master" --depth 1 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/$BITBUCKET_REPO_FULL_NAME.git $BUILD_DIR
Cloning into '/opt/atlassian/pipelines/agent/build'...

As you can see the "--depth 1" is there.

We'll probably need to create a ticket for you to allow us to investigate this case deeper and understand what is happening there.

Some questions to narrow down this one:

• Are you manually running the git commands from a script task or are you talking about the automatic checkout that happens in the build setup section?
• Is this feature working as expected for other repositories with different bitbucket-pipelines.yml (in case you have them)?