Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40959

Exception in IvyJob XMLConfigProvider: No Such Method Found

    • 1.27

      After upgrading Jenkins and all plugins, getting the exception below.

      Jenkins: 2.40
      Config File Provider: 2.15.3
      IvyPlugin: 1.26

      Workaround: downgrade Config File Provider to 2.13

      Exception
      FATAL: org.jenkinsci.plugins.configfiles.xml.XmlConfig$XmlConfigProvider.getConfigById(Ljava/lang/String;)Lorg/jenkinsci/lib/configprovider/model/Config;
      java.lang.NoSuchMethodError: org.jenkinsci.plugins.configfiles.xml.XmlConfig$XmlConfigProvider.getConfigById(Ljava/lang/String;)Lorg/jenkinsci/lib/configprovider/model/Config;
      	at hudson.ivy.IvyModuleSetBuild$RunnerImpl.doRun(IvyModuleSetBuild.java:365)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
      	at hudson.model.Run.execute(Run.java:1729)
      	at hudson.model.Run.run(Run.java:1688)
      	at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:281)
      	at hudson.model.ResourceController.execute(ResourceController.java:98)
      	at hudson.model.Executor.run(Executor.java:404)
      
      

          [JENKINS-40959] Exception in IvyJob XMLConfigProvider: No Such Method Found

          there is an open PR for this plugin to fix this issue - unfortunate it was not yet merged and I don't have permission to do so.

          https://github.com/jenkinsci/ivy-plugin/pull/23

          arothian kindly offered to merge and release the plugin, hopefully hi finds time to do so soon

          Dominik Bartholdi added a comment - there is an open PR for this plugin to fix this issue - unfortunate it was not yet merged and I don't have permission to do so. https://github.com/jenkinsci/ivy-plugin/pull/23 arothian kindly offered to merge and release the plugin, hopefully hi finds time to do so soon

          jonl_percsol please be aware: the config-file-provider integration done in the ivy-plugin was totally buggy and screwed the whole plugin when used together with any other configuration file then ivy configs. Therefore this PR also needed to fix this issues - because the integration was done so wrong, I can't guarantee data gets migrated correctly when any ivy-config are configured before the you upgrade to the newest config-file-provider plugin version.

          Dominik Bartholdi added a comment - jonl_percsol please be aware: the config-file-provider integration done in the ivy-plugin was totally buggy and screwed the whole plugin when used together with any other configuration file then ivy configs. Therefore this PR also needed to fix this issues - because the integration was done so wrong, I can't guarantee data gets migrated correctly when any ivy-config are configured before the you upgrade to the newest config-file-provider plugin version.

          Kevin Formsma added a comment -

          Should be fixed in ivy-plugin 1.27.

          Kevin Formsma added a comment - Should be fixed in ivy-plugin 1.27.

          No problem imod, this is why we keep backups, yes? Although, I am using the SCM configuration plugin and it appears that it does not backup the files from the XMLConfigProvider correctly, but I am not sure if that is due to the issues in question or something in the configuration I will need to look at. I will test the fix in ivy-plugin 1.27 as soon as it releases and I get a chance to do the update.

          Jonathon Lamon added a comment - No problem imod , this is why we keep backups, yes? Although, I am using the SCM configuration plugin and it appears that it does not backup the files from the XMLConfigProvider correctly, but I am not sure if that is due to the issues in question or something in the configuration I will need to look at. I will test the fix in ivy-plugin 1.27 as soon as it releases and I get a chance to do the update.

            arothian Kevin Formsma
            jonl_percsol Jonathon Lamon
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: