Using diff transcoding in Bitbucket Server
Administering Bitbucket Server
- Users and groups
- External user directories
- Global permissions
- Setting up your mail server
- Integrating Bitbucket Server with Atlassian applications
- Connecting Bitbucket Server to an external database
- Migrating Bitbucket Server to another server
- Run Bitbucket in AWS
- Specifying the base URL for Bitbucket Server
- Configuring the application navigator
- Managing apps
- Auditing in Bitbucket
- Updating your Bitbucket Server license details
- Bitbucket Server config properties
- Moving Bitbucket Server to a different context path
- Data recovery and backups
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Data Center Migration
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Lockout recovery process
- Proxying and securing Bitbucket Server
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket Server debug logging
- Scaling Bitbucket Server
- Add shortcut links to a Bitbucket Server 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
- Managing personal access tokens
- Connecting to a 3rd party application using Application Links
- Setting a system-wide default branch name
On this page
Related content
- No related content found
As of Bitbucket Server 3.1, Bitbucket Server supports transcoding for diffs. This allows Bitbucket Server to convert files in encodings like EUC-JP, GB18030 and UTF-16 to UTF-8, so they are processed correctly by git diff, which only supports UTF-8. Similar transcoding has been applied to Bitbucket Server's source view since it was released, so this change brings the diff view in line with the source view. Diff transcoding is applied to commit and pull request diffs, as well as the diff-to-previous view.
Git for Windows, formerly known as msysgit, has known issues with Unicode paths. Diff transcoding works on all supported versions of Git for Windows, but 1.8.0 or higher is required to support Unicode paths.
Enabling diff transcoding
Diff transcoding must be explicitly enabled for each repository (unlike source view transcoding, which is always performed).
Repository administrators can enable diff transcoding on the repository settings page:
Performance and scaling
There's a performance consideration with transcoding. It is implemented using Git's textconv support, so using it adds overhead to displaying diffs. Where possible, the best approach, given git only supports UTF-8 content, is to use UTF-8 encoding so that transcoding is not necessary. In repositories without non-UTF-8 content, diff transcoding should be left disabled. Other encodings are often a necessity, however, and for repositories containing such content enabling diff transcoding allows using the full range of Bitbucket Server features.
When transcoding is enabled, git diff writes the before and after blobs to temporary files and invokes the textconv script once for each file. The script Bitbucket Server installs uses Perl to send a request back to Bitbucket Server with the path to each temporary file. Bitbucket Server then opens each file, detects the encoding using the same algorithm the source view uses, converts the file to UTF-8 and streams it out for git diff to use. After git diff has invoked the textconv script the temporary files it created are deleted.
Writing the blobs to disk, starting Perl and calling back into Bitbucket Server are all overhead processing compared to performing a diff without transcoding. How much overhead that is varies by the size of the diff. When nominally-sized files containing two or three thousand lines or less are being compared the overhead is miniscule, under 50 milliseconds on an average server. However, when comparing larger files the overhead can result in a noticeable delay displaying the diff.
Related content
- No related content found