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

Enable disabled (transitive) dependencies when installing a new plugin

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None

      When installing a new plugin, Jenkins automatically also installs dependencies that are not installed.

      Unfortunately, it's possible to disable plugins, whose effect to the Jenkins runtime is effectively the same as if the plugin was missing – except that there's currently no process to enable plugins that are disabled.

      Similar to DownloadJobs added for missing dependencies, there should be EnableJobs that enable disabled dependencies (or another approach, but this would nicely mirror the existing DownloadJob one).

      We received multiple reports from users affected by this when upgrading to 2.0 and installing the pipeline plugins, so this is critical.

          [JENKINS-34494] Enable disabled (transitive) dependencies when installing a new plugin

          Daniel Beck created issue -

          Daniel Beck added a comment - References: https://issues.jenkins-ci.org/browse/JENKINS-34434 https://groups.google.com/forum/#!msg/jenkinsci-users/4mAzgV_HvCk/XRk-uLdUNAAJ https://www.reddit.com/r/programming/comments/4gl6cd/jenkins_20_is_here/d2ip3cy https://www.reddit.com/r/programming/comments/4gl6cd/jenkins_20_is_here/d2jpm52

          Daniel Beck added a comment -

          Daniel Beck added a comment - https://twitter.com/alexsotob/status/725425301522661376
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-34434 [ JENKINS-34434 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-32340 [ JENKINS-32340 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-21485 [ JENKINS-21485 ]

          Keith Zantow added a comment -

          Similarly, if plugin installations are not run, will detached plugins will get installed? I just thought of this as I'm looking to detach some code into a plugin for another ticket... this would leave Jenkins in a similarly bad state. As part of this PR, I think we should ensure during an upgrade, at least:

          *) required dependencies are installed
          *) required dependencies are enabled

          Keith Zantow added a comment - Similarly, if plugin installations are not run, will detached plugins will get installed? I just thought of this as I'm looking to detach some code into a plugin for another ticket... this would leave Jenkins in a similarly bad state. As part of this PR, I think we should ensure during an upgrade, at least: *) required dependencies are installed *) required dependencies are enabled
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-21486 [ JENKINS-21486 ]

          Daniel Beck added a comment -

          if plugin installations are not run, will detached plugins will get installed

          That code exists, executed during startup. It compares old Jenkins version with new Jenkins version, and installs all plugins in the "bundled" version if they've been detached between these versions.

          Daniel Beck added a comment - if plugin installations are not run, will detached plugins will get installed That code exists, executed during startup. It compares old Jenkins version with new Jenkins version, and installs all plugins in the "bundled" version if they've been detached between these versions.
          Daniel Beck made changes -
          Assignee New: Sam Van Oort [ svanoort ]

            kzantow Keith Zantow
            danielbeck Daniel Beck
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: