-
Suggestion
-
Resolution: Fixed
Hi everyone,
Git LFS file locking is supported starting from Bitbucket Server 6.3.
Details on locking and unlocking feature is here - Working with Git LFS Files.
Anton Genkin
Product Manager - Bitbucket Server
Original description is below:
The Git LFS 2.0 client has been released and supports the new Git LFS File Locking API. Bitbucket Server currently (as at version 4.14) does not support this API.
The Git LFS client, upon attempting to lock a file will report the server does not implement the locking API:
$ git lfs lock galaxy1.jpg Lock failed: Not Implemented: https://user@bitbucket.example.com/scm/myproject/lfstest.git/info/lfs/locks
SSH Caveat:
Where an SSH remote is used the error message indicating "lock failed" will be different, it will report as an "Authorization error" as below:
Lock failed: Authorization error: https://bitbucket.example.com/scm/myproject/lfstest.git/info/lfs/locks Check that you have proper access to the repository
The reason for this is, when authenticating via SSH a JWT authentication token is returned, for use on the Git LFS HTTP based APIs. While the token is valid for accessing the Batch API (for example to upload a file) it is not valid for the (non existent) /info/lfs/locks API.
- is duplicated by
-
- Closed
- is related to
-
BSERV-11059 Ensure HTTP status 404 is returned on Locking API
-
- Closed
-
- was split from
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-9623] Add support for Git LFS File Locking API
Bitbucket Server (previously known as Stash) was first released in May 2012 as an enterprise-grade, high performance, self-managed Git repository hosting and collaboration tool. It was built from the ground-up for self-managed deployment.
Bitbucket Cloud was acquired by Atlassian in 2010 and was purpose-built for the multi-tenant public cloud. As a result, Bitbucket Cloud and Bitbucket Server has different technical architectures with different feature roadmaps.
morten.stensgaard, you could vote for #14454 - Git LFS (v2.x) File Locking Support in Bitbucket Cloud.
I Assume Bitbucket Cloud is a customized version of Bitbucket Server behind the scenes
IIRC, someone from Atlassian mentioned that Bitbucket Cloud and Bitbucket Server do not share any source code. The Wikipedia article on Bitbucket says they are even implemented in different programming languages (Python vs. Java). Bitbucket.org was originally a separate company that Atlassian then acquired.
Does anyone know, when/if new features like this are released on Bitbucket Cloud? (I Assume Bitbucket Cloud is a customized version of Bitbucket Server behind the scenes - But is it behind/infront on release versions?)
Benjamin Grauer
added a comment - Totally need a firework here! Hi everyone. I'm happy to announce that Bitbucket Server 6.3 has support for Git LFS file locking!
You can now lock files stored in LFS to avoid merge conflicts. Please read the docs to learn more about locking and unlocking - Working with Git LFS Files and don't forget to share feedback on the feature. We are keen to learn if there are any areas of improvement.
To learn more about new features in Bitbucket Server 6.3 visit Release notes.
Cheers,
Anton Genkin
Product Manager Bitbucket Server
We keep on gradually improving git LFS file locking feature. In Bitbucket Server 6.4 we started to show lock icons against filenames on Source view and Source listing pages to help you spot locked files easier.
Source listing:
Source view:
To learn more about new features in Bitbucket Server 6.4 visit Release notes.
Cheers,
Anton Genkin
Product Manager Bitbucket Server