JJB doesn't handle the latest config file provider IDs for objects
properly as it expects them all to be prefixed with
org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig otherwise it
believes the information to be a file path (which doesn't work!) As
such, the honeycomb-settings ID has been fixed up to be more inline with
what JJB expects / requires (until we can get it patched). This required
a restart of Jenkins to take effect.
Change-Id: I60092b1a229d498d672b60fef9554fd7a16d5b60
Signed-off-by: Andrew Grimberg <[email protected]>
# Config File provider ID mapping
global-settings: 'org.jenkinsci.plugins.configfiles.maven.GlobalMavenSettingsConfig1449593564219'
- honeycomb-settings: 'bcd56fc8-76b4-4fa0-b2cd-c13bc5cdc527'
+ honeycomb-settings: 'org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig1452706188439972818'
vpp-settings: 'org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig1449593875850'