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

Active Choices 2.2 declares optional dependency on Scriptler but uses it non-optionally

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: active-choices-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.176.3 on Windows 7 x64
    • Similar Issues:
    • Released As:
      uno-choices 2.2.1

      Description

      Updated Description:

      Active Choices Plugin has an optional dependency on Scriptler, but this commit released in version 2.2 caused the Scriptler dependency to be used non-optionally, breaking Jenkins startup when it was used. The fix is to update to Active Choices 2.2.1

      Original Description:

      Hi,

      After Script Security 1.64 plugin update, Jenkins can't start.
      This issue doesn't exist with previous versions of this plugin.

      Unfortunately, I can't downgrade it, because I can't access the web ui (and I don't know, how to compile from it's source code).
      If I just disable it (renaming the script-security.jpi file to .jpi.disabled ) and restart jenkins, everything is working, but a lots of plugin needs this plugin to work.

       

      Could you please look after this issue?
      Thanks in advance!

        Attachments

          Activity

          Hide
          dnusbaum Devin Nusbaum added a comment -

          Csaba Berta Neither of those exceptions seem related to script-security at a glance. Do you have any other reason to believe that the problem you are seeing is related to script-security? I am surprised that you were able to restart Jenkins after disabling script-security, I would have thought that Jenkins startup would fail because of unsatisfied dependencies. Do you see any other warnings in your Jenkins logs at startup, or are the screenshots you posted the only warnings you are seeing?

          Show
          dnusbaum Devin Nusbaum added a comment - Csaba Berta Neither of those exceptions seem related to script-security at a glance. Do you have any other reason to believe that the problem you are seeing is related to script-security? I am surprised that you were able to restart Jenkins after disabling script-security, I would have thought that Jenkins startup would fail because of unsatisfied dependencies. Do you see any other warnings in your Jenkins logs at startup, or are the screenshots you posted the only warnings you are seeing?
          Hide
          fadden Csaba Berta added a comment - - edited

          Hi,

          I have attached two log, with and without script security plugin at startup.
          When I start without, everything is working well except a lot of plugin has a dependency alert because of script security

          Show
          fadden Csaba Berta added a comment - - edited Hi, I have attached two log, with and without script security plugin at startup. When I start without, everything is working well except a lot of plugin has a dependency alert because of script security
          Hide
          dnusbaum Devin Nusbaum added a comment -

          Csaba Berta I think the problem is the very first warning in the logs:

          SEVERE: Failed to create Guice container from all the plugins
          ...
          Caused by: java.lang.ClassNotFoundException: org.jenkinsci.plugins.scriptler.config.ScriptlerConfiguration
          

          It looks like this was caused by the Active Choices plugin in this commit. I'd look at https://github.com/jenkinsci/active-choices-plugin/pull/27, which should fix the issue, and looks to have been released in Active Choices 2.2.1.

          Show
          dnusbaum Devin Nusbaum added a comment - Csaba Berta I think the problem is the very first warning in the logs: SEVERE: Failed to create Guice container from all the plugins ... Caused by: java.lang.ClassNotFoundException: org.jenkinsci.plugins.scriptler.config.ScriptlerConfiguration It looks like this was caused by the Active Choices plugin in this commit . I'd look at https://github.com/jenkinsci/active-choices-plugin/pull/27 , which should fix the issue, and looks to have been released in Active Choices 2.2.1.

            People

            • Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              fadden Csaba Berta
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: