Access logs reference repositories inconsistently
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The atlassian-bitbucket-access*.log files may reference the repositories inconsistently. The same log file may reference the same repository in two different ways, for example:
git-receive-pack '/my_project/my_repo.git'
git-receive-pack '/my_project/my_repo'
Cause
The reference found in the access log is exactly the same as specified by the user.
- In the web interface, Bitbucket Server always presents repositories referenced with the extension .git
- However, in usage, this extension is optional, so the users, in their commands, scripts etc., may refer to repositories either with, or without the extension. Both notations are perfectly correct, understandable to Bitbucket, and fully functional.
In the access log, Bitbucket Server always uses the exact same notation as it was specified by the user. This explains why you may sometimes see the same repository referenced with the extension, and sometimes without it.
Resolution
If you parse the access logs for references to specific repositories, keep in mind that both valid notations should be expected.