Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

We couldn't clone the repository. Try rerunning the pipeline.

Sajith Madurachchi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 14, 2024

Hi all, 

I'm getting this error randomly while trying to run bitbucket pipelines using linux shell runner. Sometimes this can be resolved by re running pipeline but occasionally had to rebase the repository. I went through previous discussion about the same topic but Atlassian engineers haven't mentioned any reason or solution for the specific matter. Hence reposting the issue. 

cheers!  

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 16, 2024

Hi Sajith and welcome to the community!

There are multiple different things that may cause this error. Possible reasons could be:

  • The depth of the clone in this step may not be big enough for Pipelines to reset to the build's commit
  • If the build runs on a self-hosted runners and the host machine is behind a firewall, not all of Bitbucket's IP addresses may be whitelisted
  • The remote repository has broken tree entries

This is not an exhaustive list, and we cannot provide a solution without knowing what is causing the failed clone.

If you open on Bitbucket's website the page of a build that failed with this error and then expand the Build setup section in the log, is there a more informative error message there? Could you post the content of the Build setup section here (sanitize private/sensitive data first, if any)?

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events