Support Git LFS.

We are also getting the smudge filter lfs failed error when using unity cloud. We moved from a non lfs repo to a lfs one, so maybe that has something to do with it?

Running Prebuild steps
In quiet period, build will start momentarily...
Agent pid 1219
All identities removed.
Removing bvr
Successfully uninstalled bvr-1.2.12
done.
bvr 1.6.2
bvr-api 0.3.3
prebuildstatus finished successfully.
All identities removed.
Cloning the remote Git repository
Cloning repository -----------removed--------------
Fetching upstream changes from -----------removed--------------
Fetching upstream changes from -----------removed--------------
Checking out Revision -----------removed-------------- (-----------removed--------------)
FATAL: Could not checkout -----------removed--------------
at sun.reflect.GeneratedMethodAccessor244.invoke(Unknown Source)
stdout:
stderr: Downloading -----------removed-------------- (3.28 MB)
Downloading -----------removed-------------- (18.35 MB)
Error downloading object: -----------removed-------------- (-----------removed--------------)
Errors logged to -----------removed--------------
fatal: -----------removed--------------: smudge filter lfs failed
git-lfs/1.4.1 (GitHub; darwin amd64; go 1.7; git 2070e4c)
git version 2.6.6
Error downloading object: -----------removed--------------
Smudge error: Error buffering media file: LFS: Repository or object not found: -----------removed--------------
Check that it exists and that you have proper access to it:
Build step 'Execute shell' marked build as failure
postbuildstatus finished successfully.
Finished: FAILURE

 

i have exactly some issue since some days.
please, what can i do ?
i retried multiple times, but issue remain.

 

PM'd with similar issues.

 

+1 on Error downloading object" with LFS

 

I PM'd SophiaC with Unity, and she changed our project to use an improved LFS pull. It worked much better after that.

 

yes, same thing more recently.
thanks

 

Hey! We have a problem also. For testing purposes we added new file (png tex) to LFS (before that whole project was just in nornal Git repo), since then we are getting an error in Cloud Build that file cannot be read.

 

I am falling into a similar situation.
I noticed that the beginning of the log changed like this.

▼ 6Days Ago SUCSESS
4: All identities removed.
5: Removing bvr
6: Successfully uninstalled bvr-1.2.12
↓
▼ Yesterday FAILED
4: All identities removed.
5: Removing bvr
6: Successfully uninstalled bvr-1.5.21

▼ 6Days Ago SUCSESS
20: Calculated Workspace Size: 225.83 MiB
21: PATH | SIZE
22: /Assets | 224.28 MiB
23: /Evacuation | 1.52 MiB
24: /ProjectSettings | 41.10 kiB
↓
▼ Yesterday FAILED
20: Calculated Workspace Size: 34.66 MiB
21: PATH | SIZE
22: /Assets | 33.11 MiB
23: /Evacuation | 1.52 MiB
24: /ProjectSettings | 41.11 kiB

31101: Build step 'Execute shell' marked build as failure
31102: postbuildstatus finished successfully.
31103: Finished: FAILURE

After a clean build, it seems that files managed by LFS can no longer be downloaded.
Is something working on this subject?

 

Git LFS is now supported https://feedback.unity3d.com/suggestions/git-lfs-large-file-support-for-unity-cloud-build

 

Fantastic news! Giving it a try with 2 big projects right away. Thanks!

 

@SophiaC are they any know issues with LFS bit-bucket and unity cloud build ? my lfs dont seem to be getting pulled through , any idea what could be causing this ?

Getting this error in cloud build for all textures and other LFS files

[Unity] Could not create texture from Assets/Standard Assets/Effects/ImageEffects/Textures/NoiseEffectGrain.png: File could not be read

Thanks

 

I'm having the same issue!

update: upon a closer look in my case, the LFS files aren't acutally retrieved... here is a snippet of the log:


219: [03:42:45] [ INFO] Resolving deltas: 80% (29/36)
220: [03:42:45] [ INFO] Resolving deltas: 83% (30/36)
221: [03:42:45] [ INFO] Resolving deltas: 86% (31/36)
222: [03:42:45] [ INFO] Resolving deltas: 88% (32/36)
223: [03:42:45] [ INFO] Resolving deltas: 91% (33/36)
224: [03:42:45] [ INFO] Resolving deltas: 100% (36/36)
225: [03:42:45] [ INFO] Resolving deltas: 100% (36/36), done.
226: [03:42:45] [ INFO]
227: [03:42:47] [ INFO] Git LFS: (0 of 5 files) 0 B / 4.31 MB
228: [03:42:47] [ INFO] Git LFS: (0 of 5 files) 0 B / 4.31 MB
229: [03:42:47] [ INFO]
230: batch response: Post <MY URL>.git/info/lfs/objects/batch: x509: certificate signed by unknown authority
231: [03:42:47] [ INFO]
232: Cloned in 4 seconds.
233: GIT: Checkout operation complete.



The reason is rather obvious, the certificate on my server isn't being used correctly and it also happens locally. (where I had disabled it) In other words, I have to fix my server first ^^

I doubt that you have the same issue but who knows

 

This still does not work with Atlassian Bitbucket. The following error appears in the build logs:

batch request: Git LFS is not supported over SSH when using a read-only access key. For more information, see https://confluence.atlassian.com/x/RjRmMQ: exit status 1

In order to pull Git LFS files from Bitbucket, Unity Cloud Build needs to support Bitbucket App passwords:
https://confluence.atlassian.com/bi...et-AccesskeysdonotallowaccesstotheGitLFSfiles

 

I just ran into this same issue quite recently! Here's how I got LFS pulling working:

1. Before anything else, I had to learn that there's a difference between a deploy SSH key (the "read-only access key" in your build log) and a user authorization SSH key. If you use a deploy SSH key to grant Unity Cloud Build access to your repo, it won't pull LFS files. You'll have to generate a new SSH key and use it to authorize a new user.
2. Create a new Bitbucket user with read-only access to all your repos for Unity Cloud Build. This new Bitbucket account is your machine user. Unity Cloud Build will log in as this machine user and check out your repos that way. (In theory you can let Unity Cloud Build log in as your own account, but that creates all sorts of security compromises)
3. Refresh your Unity Organization SSH key. The only way to do this is through the Unity Cloud Build API. If you've never used the API before, sorry. And good luck. Remember, this step invalidates your old SSH key, so until your Machine User is up and running, none of your Unity Cloud Build projects will be able to check out code.
4. While logged in as your Machine User in Bitbucket, go to "User Settings > Security > SSH Keys" and add your new SSH key here. Do not use your new SSH key as a deploy key.

I think that's all it takes. Next time you start a Cloud Build, the server will use the SSH key to log in as your machine user, check out the latest commit from your repo (LFS files and all!), and build as normal.

 

This is seriously hampering our cloud build operations also, as builds that were working before suddenly aren't.. such a pain!

 

Thanks for the tips! I'll probably give this a shot in the next week or two and report my findings.

 

How do I connect Unity Cloud Build to a Bitbucket repository using LFS?

Access and Cloning works, but LFS files are not checked out before the build.
The build log shows:

The linked documentation page by atlassian excplicitly states :

But Unity Cloud build is set up to access the repo with an access key and I don't see an alternative.
[edit] Or even a way to change this after the fact?

[2nd edit]
Ok now I understood the proposed workaround from 3 posts earlier. But unless I want (or even can) add a dummy User to bitbucket for this access I'm stranded...
That is, until bitbucket get's it together and supports LFS checkout with ssh keys or until Unity Cloud Build can access bitbucket with an App Password.

 

I just answered that three posts up Look at post #64 in this thread.

 

Still no workaround to get Visual Studio Online LFS and Unity Cloud Build to work together?