Our Flare project is about 5M, and BB has a 2G limit. Plenty of headroom, you'd think, and yet periodically the BB repo is suddenly 1.8G. We have exceeded the 2G limit at times, at which point you are locked out and cannot push. The temporary fix is to open a support ticket with Atlassian asking them to run garbage collection - when they are done, *all* your Flare users must clone a fresh copy of the repository, move any work in progress from the old copy to the new one, and work only in the new copy.
Anyone else see this? One odd thing that may be related: from time to time, I'll push a small number of topics and the Flare progress dialog displays numbers for "bytes pushed" that are way above what they should be. Even if I abort the push, it appears to succeed - it's listed in BB Commits and the correct files appear to be committed. This might be related - I haven't nailed it down.
Anyone else seeing this? Successfully fixed it? It's causing us a lot of heartburn.
Bitbucket 2G limit
This forum is for all Flare issues related to using Source Control.
Jump to
- MadCap Flare
- ↳ Flare's General Discussion
- ↳ Getting Started and Installation Issues
- ↳ Importing
- ↳ Styles, Stylesheets and XML
- ↳ Single-Sourcing
- ↳ Web-based Outputs
- ↳ Printed Documentation Targets
- ↳ WebHelp Mobile
- ↳ DotNet Help and the Dot Net Viewer
- ↳ Microsoft CHM Help
- ↳ Source Control
- ↳ Tips and Tricks
- ↳ Simon's Career Network
- MadCap Central
- ↳ Central's General Discussion
- MadCap Doc-To-Help
- ↳ Doc-To-Help General Discussion
- ↳ Doc-To-Help Output
- MadCap Lingo
- ↳ MadCap Lingo General Discussion
- MadCap Mimic
- ↳ Mimic's General Discussion
- ↳ Mimic Output
- MadCap Capture
- ↳ Capture's General Discussion
- MadCap Analyzer
- ↳ Analyzer's General Discussion
- ↳ Analyzer Tips and Tricks
- MadCap Pulse Server and FeedBack Server
- ↳ Feedback Explorer and Server
- ↳ MadCap Pulse Server
- MadCap Contributor (X-Edit)
- ↳ Contributor General Discussion