-
Suggestion
-
Resolution: Fixed
-
None
It was going to be awesome if Stash could have git-lfs support.
This would help people who needs to work large binary files.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-4027] Support git-lfs for large file extensions
Jonathan Reyes
added a comment - Yes, crystal. Thank you very much!!! Bitbucket Server is the 4.x rebrand of Stash. No version of the product called "Stash" will ever have Git LFS. However, if you upgrade your Stash instance (major versions 1, 2 or 3) to Bitbucket Server 4.3, you'll get LFS support.
Does that help clarify?
Best regards,
Bryan Turner
Atlassian Bitbucket
Jonathan Reyes
added a comment - This is great news! How about in Stash? Do we have an ETA? Git Large File Storage (LFS) support has shipped in Bitbucket Server 4.3: https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+Server+4.3+release+notes
Vincent Thibault
added a comment - We are also waiting for this very important feature. We hope to start evaluating it soon. I'll try to illustrate why this feature could bring us major improvements to our development speed.
We started migrating from SVN to Bitbucket (Stash) and Bamboo in June 2014, and have started implementing "Gate Keepers". In our current environment, we use Pull Request in Bitbucket combined with binary files being managed in SVN. SVN is our legacy system we are migrating from, but all our binary files are still managed in SVN while our source code has been migrated into Bitbucket for the most part.
These 2 independant systems (Bitbucket and SVN) make it hard to get full benifits from "Gate Keeper" Plan Branches (where auto-merging is done only when our Bamboo build is green). The SVN commits are already done by the time the "Gate Keeper" decides to reject the "Pull Request" because of a RED build.
With the independance between "Pull Requests" in Bitbucket on one side and SVN commits on the other side, our Bamboo builds are often RED. Broken builds of our low level "Configuration Items" at the bottom of our "Configuration Items" hierarchy build dependencies is very costly. Our build times have been greatly reduced for our "incremental watchdog builds", but our "full official builds where all the various levels of automated testing are performed" are still very long. A low level "Configuration Item" red build, even when fixed immediately, means that our highest level builds in the dependency chain will only be available the next day to our QA teams. That is very costly and frustrating to our agile development teams.
I'm glad to hear Atlassian is expecting to be done in less than a year. This JIRA issue is the most important feature we are waiting for. Atlassian tools (Confluence, JIRA, Bitbucket and Bamboo) are well integrated and are providing great value to us so far. Keep up the good work.
Vincent Thibault
added a comment - We are also waiting for this very important feature. We hope to start evaluating it soon. I'll try to illustrate why this feature could bring us major improvements to our development speed.
We started migrating from SVN to Bitbucket (Stash) and Bamboo in June 2014, and have started implementing "Gate Keepers". In our current environment, we use Pull Request in Bitbucket combined with binary files being managed in SVN. SVN is our legacy system we are migrating from, but all our binary files are still managed in SVN while our source code has been migrated into Bitbucket for the most part.
These 2 independant systems (Bitbucket and SVN) make it hard to get full benifits from "Gate Keeper" Plan Branches (where auto-merging is done only when our Bamboo build is green). The SVN commits are already done by the time the "Gate Keeper" decides to reject the "Pull Request" because of a RED build.
With the independance between "Pull Requests" in Bitbucket on one side and SVN commits on the other side, our Bamboo builds are often RED. Broken builds of our low level "Configuration Items" at the bottom of our "Configuration Items" hierarchy build dependencies is very costly. Our build times have been greatly reduced for our "incremental watchdog builds", but our "full official builds where all the various levels of automated testing are performed" are still very long. A low level "Configuration Item" red build, even when fixed immediately, means that our highest level builds in the dependency chain will only be available the next day to our QA teams. That is very costly and frustrating to our agile development teams.
I'm glad to hear Atlassian is expecting to be done in less than a year. This JIRA issue is the most important feature we are waiting for. Atlassian tools (Confluence, JIRA, Bitbucket and Bamboo) are well integrated and are providing great value to us so far. Keep up the good work. We are actively working on LFS support. Unfortunately I can't provide a concrete timeframe, but I can tell you that it won't be a year.
luca14, it is not easily possible to integrate LFS with Bitbucket server and replace it with our work.
While we wait for this feature (which is quite critical for us as well). Is it possible to manually integrate git-lfs with Bitbucket server and then replace it with your work?
Can you at least give a rough estimate on when it will be implemented and available?
Is it more like 1 month or 1 year?
We're about to make a decision on which system we'll get to manage large binary files and it would be great to know.
This is excellent news !!! We were waiting for this. We will have to evaluate this new version before upgrading.