We encounter this issue also a few time ago. Root cause was rules set to our nginx reverse proxy, which was blocking transfer biggers than 1G.
I suggest that you check if you have a reverse proxy between your Bitbucket and your computer, and set up a rule to allow bigger transfer files in case of clone. Pay also attention to the timeout rule, both at NginX, but also at Bitbucket config level.
Another root cause could be your local git client settings and version, but with 1.8 or higher this should not impact you.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot