Config File Provider 3.0 introduces regressions

Issue

After upgraded Config File Provider to version 3.0 and I am observing the following elements broken or impacted:

Configuration files
Shared libraries
Per-project permissions on folders

Environment

CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller (CORE-MM)
CloudBees CI (CloudBees Core) on traditional platforms - Client controller (CORE-CM)
CloudBees Jenkins Enterprise - Managed controller
Jenkins LTS
Config File Provider 3.0

Jenkins issues

JENKINS-53399

Resolution

The CloudBees Assurance Program has excluded Config File Provider version 3.0 from its Update Center to avoid the installation.

If for some reason you have upgrades to 3.0:

Downgrade to the previous version of this plugin.
In the case any of the configuration files (jobs, folders … ) was saved after the upgrade, you have to restore jenkins from latest backup which was using the previous version of Config File Provider before the upgrade.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.