Experiencing Inconsistent and Lengthy Code Clone Times in Bitbucket Cloud CI/CD: Seeking Solutions

[Oguz Gurler]

Our Bitbucket Cloud CI/CD pipeline, utilizing self-hosted runners, occasionally faces significant code cloning delays leading to timeouts, even with depth 2 cloning. Any suggestions or experiences from the community to enhance the cloning process's consistency and speed?

[Theodora Boudale]

Hi Oguz and welcome to the community.

There are several factors that could affect this and several things to look into.

1. What type of runners are you using and are you using a supported platform as per https://support.atlassian.com/bitbucket-cloud/docs/runners/?

I've seen a similar report when Linux Docker Runners were used in a MacOS (which is not officially supported for Linux Docker Runners). In the case of MacOS (and also Windows), Docker runs in a Virtual Machine which can affect performance.

2. Do you have more than one runner on the same host?

3. Do you run builds on multiple different repos? If so, does the issue seem to occur only with one specific repo, or not?

4. What is the CPU and memory usage of the host machine when the issue occurs? If they are close to the limit, this might slow things down.

5. What is the network bandwidth usage when the issue occurs? If that is high, it could also affect the clone times.

6. It is also possible that this occurs due to a network issue that doesn't have to do with bandwidth usage, but with routing from your network to Bitbucket.

Kind regards,
Theodora