Repository is not updated by pushing content immediately after its creation
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Repositories are not updated when changes are pushed into it immediately after their creation and the initial screen is always displayed. The content is only accessible after restarting Bitbucket Server.
Figure 1: initial screen example immediately after a repository creation.
Causes and Resolutions
Bitbucket Server relies on hook scripts that are installed into each repository (and managed by the system) to provide change information that, in turn, allows it to update the repositories, pull requests and check branch permissions. If the hooks are not installed correctly, or are damaged, these required callbacks do not happen and the functionality associated with them fails.
Resolution
Follow the steps in
Git hook scripts are not executing after upgrading to Bitbucket Data Center 8.x
to identify and fix problems with the git hooks.
If the Git hook scripts are executing correctly, review the BSERV-10791 - The overview page of an existing repository shows up as an empty repository / as a new repository bug and try to apply the suggested workaround.
Was this helpful?