Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Shallow clone for pipelines is removing version tags

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:$

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?

1 answer

1 accepted

0 votes
Answer accepted
davina Atlassian Team Apr 16, 2019

Hi @davidsewell 

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

depth: full

You can find the documentation here 

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.

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events