Clean up sys_upgrade_history

[Karine_M]

Hi,

After updating a plugin, I can find the changes applied in the sys_upgrade_history table. It is then possible to process the changes_skipped in the same way as during an upgrade.
I realize that this information is deleted after X days. Only the information related to the plugins or the application of update set is deleted. The data related to version upgrades remains available.

Do you know what process deletes this data? (I would like to at least extend the retention period of this data on our non production instance).

Regards,

Karine

[James Fricker]

Clean Update History / Upgrade History retention

Behaviour is configurable via system properties:

glide.sys_upgrade_history.release.retention

(Default:10) - number of upgrade history records retained

glide.sys_upgrade_history.plugin.retention

(Default:100) - number of non-upgrade history records retained.

non-upgrade history refers to following types: Applications, Plugins, Source Control, Update Sets

Above are the recommended default limits. Increasing the values of these properties results in retaining more records in both the sys_upgrade_history and the sys_upgrade_history_log tables. The sys_upgrade_history_log table can be large as it stores the some XML payloads, so increasing value of these properties will result in a higher database storage usage.

So the upgrade history retention is not time based, but based on a count of records of different types.