For about a week or so we have sporadic failures on our SppVeyor server when cloning our repository. When it happens the message is always the same
batch response: Post https://bitbucket.org/user/repo.git/info/lfs/objects/batch: read tcp 220.127.116.11:1051->18.104.22.168:443: i/o timeout
We're cloning the repository with
git lfs clone --branch=foo https://bitbucket.org/user/repo
The version of git on AppVeyor is currently 2.13.0(2) and git lfs is 2.1.0
Is there anything that can be done to check whether this is a problem on Bitbucket or AppVeyor? It only started occurring about 5 days ago and since then it breaks our builds multiple times a day because checked out binary files end up corrupted. I couldn't find a way to run something like an LFS integrity check on the bitbucket interface.
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot