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

Unable to store any configuration with priority sorter plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • prioritysorter-plugin
    • 4.0.1 released Nov 27, 2021

      Whenever I am trying to save a configuration (job, plugin, etc.), jenkins tells me an oopsie.

      I attached example logs. In the end it always tells me something like:

      Caused: java.lang.IllegalArgumentException: Class [<A Bunch of classes here>] is specified in JSON, but no such class found in classLoader hudson.PluginManager$UberClassLoader.

      I tried upgrading/downgrading several plugins, but in the end it doesn't matter. As soon as I press a save/apply button the error appears and my changes do not take effect.

        1. README
          0.6 kB
          Mark Waite
        2. plugins.txt
          3 kB
          Mark Waite
        3. advanced-build-queue.log
          11 kB
          Norman Specht
        4. jenkins_save_job.log
          13 kB
          Norman Specht

          [JENKINS-67218] Unable to store any configuration with priority sorter plugin

          Norman Specht created issue -

          Norman Specht added a comment - - edited

          I downgraded to

          2.318 ... bug is gone

          2.319 ... bug is gone

          2.320 ... bug appears

          Norman Specht added a comment - - edited I downgraded to 2.318 ... bug is gone 2.319 ... bug is gone 2.320 ... bug appears

          Basil Crow added a comment -

          The frontend is sending values like

          {
  "stapler-class": [
    "jenkins.advancedqueue.jobinclusion.strategy.AllJobsJobInclusionStrategy",
    "jenkins.advancedqueue.jobinclusion.strategy.PropertyBasedJobInclusionStrategy",
    "jenkins.advancedqueue.jobinclusion.strategy.FolderBasedJobInclusionStrategy",
    "jenkins.advancedqueue.jobinclusion.strategy.ViewBasedJobInclusionStrategy"
  ],
  "$class": [
    "jenkins.advancedqueue.jobinclusion.strategy.AllJobsJobInclusionStrategy",
    "jenkins.advancedqueue.jobinclusion.strategy.PropertyBasedJobInclusionStrategy",
    "jenkins.advancedqueue.jobinclusion.strategy.FolderBasedJobInclusionStrategy",
    "jenkins.advancedqueue.jobinclusion.strategy.ViewBasedJobInclusionStrategy"
  ]
}

          and

          {
  "override": false,
  "": [
    "0",
    "0"
  ],
  "settings": {
    "stapler-class": [
      "jenkins.mvn.DefaultSettingsProvider",
      "jenkins.mvn.FilePathSettingsProvider",
      "org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider"
    ],
    "$class": [
      "jenkins.mvn.DefaultSettingsProvider",
      "jenkins.mvn.FilePathSettingsProvider",
      "org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider"
    ]
  },
  "globalSettings": {
    "stapler-class": [
      "jenkins.mvn.DefaultGlobalSettingsProvider",
      "jenkins.mvn.FilePathGlobalSettingsProvider",
      "org.jenkinsci.plugins.configfiles.maven.job.MvnGlobalSettingsProvider"
    ],
    "$class": [
      "jenkins.mvn.DefaultGlobalSettingsProvider",
      "jenkins.mvn.FilePathGlobalSettingsProvider",
      "org.jenkinsci.plugins.configfiles.maven.job.MvnGlobalSettingsProvider"
    ]
  }
}

          to the backend. The stapler-class and $class values should be a single string, not a list. I suspect something has gone wrong on the frontend. CC timja

          Basil Crow added a comment - The frontend is sending values like { "stapler-class" : [ "jenkins.advancedqueue.jobinclusion.strategy.AllJobsJobInclusionStrategy" , "jenkins.advancedqueue.jobinclusion.strategy.PropertyBasedJobInclusionStrategy" , "jenkins.advancedqueue.jobinclusion.strategy.FolderBasedJobInclusionStrategy" , "jenkins.advancedqueue.jobinclusion.strategy.ViewBasedJobInclusionStrategy" ], "$class" : [ "jenkins.advancedqueue.jobinclusion.strategy.AllJobsJobInclusionStrategy" , "jenkins.advancedqueue.jobinclusion.strategy.PropertyBasedJobInclusionStrategy" , "jenkins.advancedqueue.jobinclusion.strategy.FolderBasedJobInclusionStrategy" , "jenkins.advancedqueue.jobinclusion.strategy.ViewBasedJobInclusionStrategy" ] } and { "override" : false , "": [ "0" , "0" ], "settings" : { "stapler-class" : [ "jenkins.mvn.DefaultSettingsProvider" , "jenkins.mvn.FilePathSettingsProvider" , "org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider" ], "$class" : [ "jenkins.mvn.DefaultSettingsProvider" , "jenkins.mvn.FilePathSettingsProvider" , "org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider" ] }, "globalSettings" : { "stapler-class" : [ "jenkins.mvn.DefaultGlobalSettingsProvider" , "jenkins.mvn.FilePathGlobalSettingsProvider" , "org.jenkinsci.plugins.configfiles.maven.job.MvnGlobalSettingsProvider" ], "$class" : [ "jenkins.mvn.DefaultGlobalSettingsProvider" , "jenkins.mvn.FilePathGlobalSettingsProvider" , "org.jenkinsci.plugins.configfiles.maven.job.MvnGlobalSettingsProvider" ] } } to the backend. The stapler-class and $class values should be a single string, not a list. I suspect something has gone wrong on the frontend. CC timja
          Basil Crow made changes -
          Labels New: regression

          Mark Waite added a comment -

          I'm unable to duplicate the issue with Jenkins 2.322 and the list of plugins you've provided (thanks for providing that list!).

          Two of the plugins have known security issues, so should probably be removed. However, I don't think they are the likely cause of the issue.

          Can you describe more about your configuration? I see mention of job inclusion strategy and don't see a place to configure that in my Jenkins instance

          Mark Waite added a comment - I'm unable to duplicate the issue with Jenkins 2.322 and the list of plugins you've provided (thanks for providing that list!). Two of the plugins have known security issues, so should probably be removed. However, I don't think they are the likely cause of the issue. Can you describe more about your configuration? I see mention of job inclusion strategy and don't see a place to configure that in my Jenkins instance

          Tim Jacomb added a comment - - edited

          Likely another duplicate of https://issues.jenkins.io/browse/JENKINS-67109 fixed in 2.321

          Tim Jacomb added a comment - - edited Likely another duplicate of https://issues.jenkins.io/browse/JENKINS-67109 fixed in 2.321

          Mark Waite added a comment -

          I tried my same steps with the list of plugins and Jenkins 2.320 and was still unable to duplicate the issue as reported. Additional insights on the configuration of the system may help me understand how my test environment is different from yours.

          Mark Waite added a comment - I tried my same steps with the list of plugins and Jenkins 2.320 and was still unable to duplicate the issue as reported. Additional insights on the configuration of the system may help me understand how my test environment is different from yours.

          Norman Specht added a comment -

          Sorry I don't know what exactly I have to send you in order to reproduce the error. Its a debian linux with plenty of RAM and CPU power, only having jenkins running on it.

          All I can tell you the advanced-build-queue.log is taken when I try to configure exactly this plugin (advanced-build-queue).

          I took the other log by just opening the configuration of a multi-branch-pipeline job and just hit apply, but also appears when I try to configure a normal job.

          If you need more details, let me know what I should provide you.

           

          I don't think it's a duplicate of JENKINS-67109, as the bug appears also on other configuration steps and plugins and does also appear on 2.321.

          I also upgraded to 2.322, the bug still does appear making 2.319 the latest version I can use.

          Norman Specht added a comment - Sorry I don't know what exactly I have to send you in order to reproduce the error. Its a debian linux with plenty of RAM and CPU power, only having jenkins running on it. All I can tell you the advanced-build-queue.log is taken when I try to configure exactly this plugin (advanced-build-queue). I took the other log by just opening the configuration of a multi-branch-pipeline job and just hit apply, but also appears when I try to configure a normal job. If you need more details, let me know what I should provide you.   I don't think it's a duplicate of JENKINS-67109 , as the bug appears also on other configuration steps and plugins and does also appear on 2.321. I also upgraded to 2.322, the bug still does appear making 2.319 the latest version I can use.

          Mark Waite added a comment -

          I can't find a plugin named "advanced-build-queue". It is not mentioned in your list of plugins and does not appear on the Jenkins plugins site. Possibly that is a custom plugin that has been built locally?

          If that is a locally built plugin, you may want to check to see if it is the root of the issues. Remove that plugin from a test installation of Jenkins and see if the problem is resolved.

          Mark Waite added a comment - I can't find a plugin named "advanced-build-queue". It is not mentioned in your list of plugins and does not appear on the Jenkins plugins site. Possibly that is a custom plugin that has been built locally? If that is a locally built plugin, you may want to check to see if it is the root of the issues. Remove that plugin from a test installation of Jenkins and see if the problem is resolved.

          Norman Specht added a comment -

          Sorry, its the Priority Sorter Plugin

          Norman Specht added a comment - Sorry, its the  Priority Sorter Plugin

            markewaite Mark Waite
            vralfy Norman Specht
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: