Issues with not displaying old changes
I am experiencing a critical issue with TeamCity, where old changes (3 years ago) are no longer being displayed in the changelog, and as a result, links to old YouTrack tickets are no longer functioning. This issue has made it difficult to support our project, as we rely heavily on these changelogs for tracking and linking to past issues. Is there a way to rescan the vcs (git repository) and update these old builds?
Please sign in to leave a comment.
Were there any changes made, after which you weren't able to see the old changes in the changelog?
TeamCity does not load the commits which were made before the VCS root has been created. However, if the changes in question were shown earlier, this seems like not the case, and I'm not sure what could cause it, so I need more information on this issue. Thank you!
Best regards,
Anton
Hi Anton,
thanks for your quick reply. I can't rule out that we have recreated the VCS root, if by that you mean that it is being recreated in Teamcity. We have had some updates to Teamcity recently and also a move of our Git server. Unfortunately the audit log does not go back far enough. Is there any way to include these commits again?
Greetings
Sebastian
There is a related feature request: https://youtrack.jetbrains.com/issue/TW-8482/Generate-history-from-VCS-root. It is pretty old, and there is a workaround available in the comments, but I can't guarantee that it will work with the new versions. It may still be worth trying, as the workaround requires the newly created VCS root, so it won't break the current VCS root.
Unfortunately, there is no out-of-the-box functionality to easily retrieve all the VCS history.
Best regards,
Anton
Hi Anton,
thanks we will investigate in that and keep you all up to date.
Regards
Sebastian
Hi again,
unfortunately, the problem persists. Apparently, the changes are deleted exactly after 3 years (see screenshot). However, I can’t find any setting in TeamCity. All possible settings are set to “never delete.” I also seem to recall that this all started with an update about 2 years ago. Is there any setting I might have overlooked?
(The changes from 12 Sep are not showing up anymore.)
Regards
Sebstian
By default, TeamCity unloads all commits older than 3 years from the in-memory cache and performs cleanup of the commit files for the commits older than 3.5 years.
This can be controlled with the following internal properties:
`teamcity.vcsModification.maxAgeDays` - this one controls the timestamp of the older commit that should be loaded from DB on start, it is set to 3 years (in days) by default.
`teamcity.vcsModification.changedFilesCleaner.maxAgeDays` - this one specifies the date of the oldest commit from where the data should be cleaned up. By default, it is set to the value of the first property + 180 days.
These properties require a server restart to be applied.
About internal properties: https://www.jetbrains.com/help/teamcity/server-startup-properties.html#TeamCity+Internal+Properties
Best regards,
Anton