Shallow clone for pipelines is removing version tags

[davidsewell]

I have a problem using tags to automatically determine the build version. The tag list is empty when I run pipelines if there have been more than 50 commits since the last version tag. I use tags during the build to determine the version number. The problem is the clone command for pipelines is a shallow clone limited by --depth 50.

This is the clone command from the build setup log.

git clone --branch="test_tags" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/company/product.git

So if the repo has more than 50 commits since the last version tag then the tags are missing at build time so I can't automatically determine the version number.

Is there a way to remove or increase the shallow clone limit for pipelines?

[davina · Accepted solution]

Hi @davidsewell 

You can specify the clone depth by configuring a number, or `full` if you want to clone everything:

clone:
  depth: full

You can find the documentation here https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html#Configurebitbucket-pipelines.yml-ci_clone 

[Paul Davis]

I feel like there should be a keyword to clone to the last available tag from the current branch. That would allow a shallow clone while still allowing tags to be used in the pipeline.

[mwatson]

See also https://support.atlassian.com/bitbucket-cloud/docs/bitbucket-pipelines-faqs/#If-I%E2%80%99ve-pushed-a-Git-annotated-tag-in-my-Pipeline-step--why-can%E2%80%99t-I-retrieve-it-in-a-subsequent-step