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

Why is pipeline runner getting authentication error on cloning repo?

+ GIT_LFS_SKIP_SMUDGE=1 retry 6 git clone --branch="stable" --depth 50 https://x-token-auth:$$BITBUCKET_REPO_FULL_NAME.git $BUILD_DIR

Cloning into '/opt/atlassian/pipelines/agent/build'...

fatal: Authentication failed for ''

Attempt 1 of 6 failed.

Retrying in 1 seconds

Cloning into '/opt/atlassian/pipelines/agent/build'...

4 answers

1 accepted

1 vote
Answer accepted
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 25, 2022

Hi @Pratyush Raizada and @Jiří Turyna 

There seems to be a problem with bitbucket. Subscribe here for more updates.

Thanks for the reference.

Same here.

This error consumed almost 2h of build time today.


Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 26, 2022

Hi @calil.amaral and anyone else affected by this issue:

Builds that end in "System error" should not detract build minutes from your workspace.

If you see that this is not the case, or if you manually stopped affected builds during the incident, you can raise a ticket with the support team.

You can create a ticket via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.

Please provide the URLs of affected builds and we can check if they consumed build minutes, and if so, what options there are for a refund.

Kind regards,

The issue is fixed, thank Atlassian team!

Same problem here

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events