arothian I'm the maintainer of the config-file-provider plugin and I just did a major update of the same plugin. It will now support folders and configuration files on folder scope.

While working on it I came across the integration of the config-file-provider into the ivy plugin. For what I can see, the implementation is very faulty and not compatible with the other xml configuration files provided by it. (also see JENKINS-35139, JENKINS-37046).

Because of the current implementation I'm not able to properly migrate the existing configurations to the new format.

I did all required changes on the ivy plugin to fix the above issues, but this will require the ivy plugin to upgrade to a more resent jenkins core (1.642.3) - WDYT?

imod Thanks for the message. I'm not actively using the Ivy plugin myself anymore; that said, I'm happy to help merge in any PRs on the repo and push out new versions. If you have the fixes, I don't have any qualms about updating the plugin to require a newer jenkins core.

arothian many thanks for your help!!! I just released a first beta version of the config-file-provider-plugin and created a PR for the ivy-plugin: https://github.com/jenkinsci/ivy-plugin/pull/23

This PR depends on the 2.14-beta version of the config-file-provider-plugin. Please test it with this one and hold the proper release until I released the config-file-provider-plugin with a stable version.

If you like, you could do a beta release of the ivy-plugin too: https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/

arothian version 2.15 of config-file-provider is now released, feel free to do a release of your plugin to keep compatibility. The PR is uptodate: https://github.com/jenkinsci/ivy-plugin/pull/23

Code changed in jenkins
User: imod
Path:
build.gradle
http://jenkins-ci.org/commit/ivy-plugin/f5edb34584fe04e760975f3962d6efcabfb4fc50
Log:
[FIXED JENKINS-37046] [FIXED JENKINS-35139] [FIXED JENKINS-34192] update to released config-file-provider

Should be fixed in ivy-plugin 1.27.