[JENKINS-61688] Global build discarders configuration isn't loaded from disk #11436

The global build discarder configuration gets saved, but it's never loaded.

On every restart, Jenkins 2.221+ will always start with the "Job Build Discarder" configured, which means

• Any custom global build discarder configuration is lost
• Users who don't want background build discarders get the default one.

The latter is especially annoying given that we warn against potential data loss in changelog ( https://jenkins.io/changelog/#v2.221 ) and upgrade guide (https://jenkins.io/doc/upgrade-guide/2.222/#old-builds-may-be-deleted-by-global-build-discarders ). Even one-time vigilance on update won't be good enough to prevent potentially undesirable outcomes.

Originally reported by danielbeck, imported from: Global build discarders configuration isn't loaded from disk

• assignee: danielbeck
• status: Resolved
• priority: Critical
• component(s): core
• label(s): 2.222.2-fixed
• resolution: Fixed
• resolved: 2020-03-28T18:19:21+00:00
• votes: 0
• watchers: 4
• imported: 2025-11-24

Raw content of original issue

The global build discarder configuration gets saved, but it's never loaded.

On every restart, Jenkins 2.221+ will always start with the "Job Build Discarder" configured, which means

	
Any custom global build discarder configuration is lost
	
Users who don't want background build discarders get the default one.



The latter is especially annoying given that we warn against potential data loss in changelog ( https://jenkins.io/changelog/#v2.221 ) and upgrade guide (https://jenkins.io/doc/upgrade-guide/2.222/#old-builds-may-be-deleted-by-global-build-discarders ). Even one-time vigilance on update won't be good enough to prevent potentially undesirable outcomes.

• environment: 2.222.1