Git Virtual File System (GVFS)
Administer Bitbucket Data Center
- Users and groups
- Advanced repository management
- External user directories
- Global permissions
- Setting up your mail server
- Integrate with Atlassian applications
- Connect Bitbucket to an external database
- Migrating Bitbucket Data Center to another server
- Migrate Bitbucket Server from Windows to Linux
- Run Bitbucket in AWS
- Specify the Bitbucket base URL
- Configuring the application navigator
- Managing apps
- View and configure the audit log
- Monitor security threats
- Update your license key
- Configuration properties
- Change Bitbucket's context path
- Data recovery and backups
- Disable HTTP(S) access to Git repositories
- Mirrors
- Bitbucket Mesh
- Export and import projects and repositories
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enable SSH access to Git repositories
- Signed system commits
- Secret scanning
- Use diff transcoding
- Change the port Bitbucket listens on
- Lockout recovery process
- Configure secure administrator sessions (websudo)
- Proxy and secure Bitbucket
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket guardrails
- Enable debug logging
- Scaling Bitbucket Data Center
- Add a shortcut link to a repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- Configuring Project links across Applications
- Improving instance stability with rate limiting
- Use a CDN with Atlassian Data Center applications
- Manage keys and tokens
- Link to other applications
- Setting a system-wide default branch name
- Automatically decline inactive pull requests
- Secured secrets by default
- Secure Bitbucket configuration properties
- Data pipeline
- Monitor application performance
- Xcode for Bitbucket Data Center
On this page
Related content
- Unable to merge a pull request when using the Required Builds merge check in Bitbucket Data Center
- Missing commits in Bitbucket after a filesystem migration
- Commits missing from Pull Request merge on target branch
- Repository has invalid reflog entry
- Missing Pull Requests in Bitbucket Server
- How to diagnose/debug issues with Pull Request rescoping in Bitbucket Data Center
- Bitbucket Server REST API for merging Pull Request fails
- Recent commits are not visible in pull-requests for all repositories in Bitbucket 8.x
- Pull request tree and user mentions not working after upgrade
- MalformedInputException when comparing branches
Microsoft has developed an open source project called GVFS (Git Virtual File System) that helps with developer productivity when it comes to very large monolithic codebases in Git.
GVFS virtualizes the file system underlying Git repositories on developers’ machines, making more efficient use of bandwidth, space and computation by only transferring and working with files that have been accessed.
The Atlassian Marketplace provides an experimental app for Bitbucket Data Center that adds the server-side support needed to serve GVFS-enabled Git clients. It can be installed on any supported server platform and once installed, Bitbucket will handle GVFS protocol requests for any repository without any additional setup, from properly configured Git clients.
For more information about setting up GVFS on the client side, please see the blog post and linked resources from Microsoft. As at October 2017, only Windows client support was available. Sourcetree 2.0 and above for Windows is also GVFS aware when used with a GVFS enabled client.
Like GVFS itself, the experimental app is relatively new, and unsupported. It is an experimental technology preview not intended for production use, though being a distinct code path it is unlikely to introduce side effects for non-GVFS users on a production instance. If you work on large repositories, we’d love for you to take it for a spin and send us your feedback.
Related content
- Unable to merge a pull request when using the Required Builds merge check in Bitbucket Data Center
- Missing commits in Bitbucket after a filesystem migration
- Commits missing from Pull Request merge on target branch
- Repository has invalid reflog entry
- Missing Pull Requests in Bitbucket Server
- How to diagnose/debug issues with Pull Request rescoping in Bitbucket Data Center
- Bitbucket Server REST API for merging Pull Request fails
- Recent commits are not visible in pull-requests for all repositories in Bitbucket 8.x
- Pull request tree and user mentions not working after upgrade
- MalformedInputException when comparing branches