Git-clone step times out after 90 minutes

[gaborwnuk]

Bitrise Build Issue Report template

Description of the issue

git-clone step takes absurd amount of time even though i’ve set CloneDepth: 1. Repo itself isn’t anything huge and the biggest problem is it either times out after 90 minutes or passes flawlessly in around 8 minutes (still long, but hey).

Sadly, my contact with customer care team is less than perfect. I’ve reported this problem on 20th of September and until now the only request was to enable support user access (on 23rd of September). Still waiting for any data i could use to debug the issue.

Environment:

Where did the issue happen?

Stack: Visual Studio for Mac, installed on macOS 10.14.4 (Mojave), set to the Stable channel.

Which build Step causes the issue and which version of the step?

E.g.: Git Clone v4.0.17

Reproducibility

• _Does a “Rebuild” help? NO
• _Does a rebuild without caches help? NO
• Does the issue happen sporadically, or every time? : During the last 7 days - stack worked flawlessly only yesterday evening (23rd September). Rest of the week it was timing out constantly.
• Does upgrading the build Step to the latest version help? : NO
• When did the issue start? : After 6th of September.

Example builds:

• https://app.bitrise.io/build/a82e56c0e9b7a845#?tab=log - timeout
• https://app.bitrise.io/build/b4626f036311cd16#?tab=log - timeout
• https://app.bitrise.io/build/8166d1e3e14ede54#?tab=log - git clone took over 50 minutes
• https://app.bitrise.io/build/6d7ad21ac4eb0a38 - git clone took 5 minutes

Local reproduction

Works perfectly when executed locally on my mac.

Local reproduction: Linux / Android (docker based) stack builds

Works perfectly when executed locally on my mac.

Build log

Full build logs available under links attached above.

[ahvth-bitrise]

Hi @gaborwnuk , if you get a chance to get some info on what access restrictions or network topology may be present to complicate this, please feel free to re-open our conversation in Intercom.

Just a note for any users who may find this: self-hosted repositories and associated network configurations can sometimes cause anomalies if the repo is very big/complicated. In this case we experienced a git fetch hanging for 90 minutes, with no configuration errors in the workflow. Please make sure to check with your sysadmin to see if any performance/firewall/network topology restrictions are in place that may complicate a pull from a VM running in North America.