LFS for Enterprises

Description

Large enterprises that deal with a lot of binaries in their repositories struggle to move to Git, as its large file support is lacking. We should help them move to Git LFS and make sure LFS is easy and scalable to use.

Proposal

We recently launched object storage for LFS.

The next steps:

  • make it easier to see and index what is / isn't in LFS https://gitlab.com/gitlab-org/gitlab-ce/issues/15567
  • support Git LFS 2 (incl file locking) https://gitlab.com/gitlab-org/gitlab-ce/issues/35856, https://gitlab.com/gitlab-org/gitlab-ee/issues/1830
  • offer a migration tool to move repositories to LFS (Bitbucket has a great tutorial on this)

Roadmap:

  • mirror LFS objects https://gitlab.com/gitlab-org/gitlab-ee/issues/1290
  • archive includes LFS objects https://gitlab.com/gitlab-org/gitlab-ce/issues/14261
    • blocked: git archive doesn't support this, git lfs archive is a possible LFS roadmap candidate https://github.com/git-lfs/git-lfs/blob/master/ROADMAP.md

Ideas:

  • custom Git LFS media adapter https://gitlab.com/gitlab-org/gitlab-ce/issues/26793

Links / references

Documentation blurb

Overview

What is it? Why should someone use this feature? What is the underlying (business) problem? How do you use this feature?

Use cases

Who is this for? Provide one or more use cases.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

  • Feature assurance
  • Documentation
  • Added to features.yml
Edited Nov 28, 2017 by James Ramsay (ex-GitLab)
Assignee Loading
Time tracking Loading