A potential workaround is to install git lfs as part of your build or build a docker image with git lfs and use that image. You could then clone these artifacts manually in the build. It is important to remember that there is only 4GB of space available for your build.
Presently Git LFS is not usable within Pipelines. If this is a feature you would like please raise a feature request on https://bitbucket.org/site/master
As for the workaround, I've already tried this, but how you are supposed to access the credentials the Bitbucket needs for external (= git-lfs pull from the runnin docker container) access?
This will happen without credentials:
trace git-lfs: HTTP: 401 trace git-lfs: HTTP: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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