You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.