Git repository on Fisheye shows changed 0 files after indexing is completed
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
Summary
The Git repository on Fisheye/Crucible after indexing is completed, shows the correct commits IDs, but the changed files are shown as 0 on the Fisheye Git repository > Activity tab > Commits view.
Also, the changesets are not listed for adding to the Crucible Reviews
Environment
4.x
Diagnosis
Fisheye logs show WARN messages related to the Indexing of the problematic Git repo; since the Include/Exclude paths are defined incorrectly, Fisheye is unable to find the parent commit IDs of the commits it's trying to index.
1
2
3
2022-12-10 14:14:29,498 WARN [qtp1975873209-232 ] fisheye CommonChangeSetDAO-loadAttributes - Cannot resolve changeset parent id 2d14d7c068a350c70efb2c9efc7e808741df4f4b for changeset cf5b182d3a55a80ec1bb4aeb159f7238026f71d7 in TDA
2022-12-10 14:15:21,341 WARN [qtp1975873209-804 ] fisheye CommonChangeSetDAO-loadAttributes - Cannot resolve changeset parent id 2d14d7c068a350c70efb2c9efc7e808741df4f4b for changeset cf5b182d3a55a80ec1bb4aeb159f7238026f71d7 in TDA
2022-12-10 14:15:26,162 WARN [qtp1975873209-613 ] fisheye CommonChangeSetDAO-loadAttributes - Cannot resolve changeset parent id 2d14d7c068a350c70efb2c9efc7e808741df4f4b for changeset cf5b182d3a55a80ec1bb4aeb159f7238026f71d7 in TDACause
Possible misconfiguration of Include/Exclude paths for the problematic Git repo, the full absolute path of the directory must be defined here and if configured incorrectly it could lead to this issue
Solution
Fix the Include/Exclude paths values mentioned for the Git repository correctly to point to the correct directory paths and reindex the repository again for the changes to take effect.
Was this helpful?