TeamCity doesn't display changes (commits) older than three years

Symptoms

• There is a build that was finished more than three years ago.
• All clean-up settings are set to preserve all available build information.
• The build doesn't display the changes/commits it was built on.

Cause

By default, TeamCity unloads all commits older than 3 years from the in-memory cache and cleans the data related to the commits that are older than 3.5 years.

Resolution

This can be controlled with the following internal properties:

• teamcity.vcsModification.maxAgeDays: controls the timestamp of the oldest commit that should be loaded from the database on the server startup. The default value is 1080 (3 years).
• teamcity.vcsModification.changedFilesCleaner.maxAgeDays: specifies the date of the oldest commit from which the data should be cleaned up. The default value is teamcity.vcsModification.maxAgeDays+180.

These properties require a server restart to be applied.

Additional information

vcs_change database table clean-up

Cleanup vcs_change table for old/expired commits