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

Unbundled / implicit plugin dependencies may be installed multiple times

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • windows
      2.0-beta-1

      Run jenkins on windows (java -jar ...) in a clean jenkins home

      select a few plugins (pipeline - and something that depends on OWASP Markup Formatter)

      wait for the plugins to install
      create a new user

      Get told Jenkins is ready to use

      Rejoice

      Expected results

      Jenkins is ready to use with the plugins you installed

      Actual results

      A restart is required

      Go to http://localhost:8080/updateCenter/ and look at the status of plugins (may need to install another plugin)
      However you can see that

      • OWASP Markup Formatter Plugin antisamy-markup-formatter plugin is already installed. Jenkins needs to be restarted for the update to take effect
      • Pipeline workflow-aggregator plugin is already installed. Jenkins needs to be restarted for the update to take effect

      Both of these are incorrect.

      The wizard has requested the same version be installed multiple times.
      You can see this if you go to /pluginManager/installed and version 1.3 is installed - yet you can download to 1.3....

      So
      1) Jenkins should restart if it has installed plugins that require a restart to activate
      2) Jenkins should not try to install the same version of the plugin twice (infact it should not try to install any version of the same plugin twice - do it once and install the latest).

      For slow internet links the multiple isntalls will cause a longer than required setup time.

          [JENKINS-33950] Unbundled / implicit plugin dependencies may be installed multiple times

          James Nord created issue -
          James Nord made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Spike Washburn made changes -
          Labels Original: 2.0 2.0-beta New: 2.0 2.0-beta community-bee

          Keith Zantow added a comment -

          teilo I have not observed this behavior in the latest versions of the setup wizard, even when installing everything, it simply tells you "Jenkins is ready" and lets you continue to the app. Can we close this issue?

          Keith Zantow added a comment - teilo I have not observed this behavior in the latest versions of the setup wizard, even when installing everything, it simply tells you "Jenkins is ready" and lets you continue to the app. Can we close this issue?

          James Nord added a comment -

          let me re-test with beta-2

          James Nord added a comment - let me re-test with beta-2
          James Nord made changes -
          Description Original: Run jenkins on windows (java -jar ...) in a clean jenkins home

          select a few plugins (pipeline - and something that depends on OWASP Markup Formatter)

          wait for the plugins to install
          create a new user

          Get told Jenkins is ready to use

          Rejoice

          h3. Expected results

          Jenkins is ready to use with the plugins you installed

          h3. Actual results

          A restart is required :-(

          Go to http://localhost:8080/updateCenter/ and look atht e status of plugins (may need to install another plugin)
          However you can see that

          * OWASP Markup Formatter Plugin antisamy-markup-formatter plugin is already installed. Jenkins needs to be restarted for the update to take effect
          * Pipeline workflow-aggregator plugin is already installed. Jenkins needs to be restarted for the update to take effect

          Both of these are incorrect.

          The wizard has requested the same version be installed multiple times.
          You can see this if you go to /pluginManager/installed and version 1.3 is installed - yet you can download to 1.3....

          So
          1) Jenkins should restart if it has installed plugins that require a restart to activate
          2) Jenkins should not try to install the same version of the plugin twice (infact it should not try to install any version of the same plugin twice - do it once and install the latest).

          For slow internet links the multiple isntalls will cause a longer than required setup time.

          New: Run jenkins on windows (java -jar ...) in a clean jenkins home

          select a few plugins (pipeline - and something that depends on OWASP Markup Formatter)

          wait for the plugins to install
          create a new user

          Get told Jenkins is ready to use

          Rejoice

          h3. Expected results

          Jenkins is ready to use with the plugins you installed

          h3. Actual results

          A restart is required :-(

          Go to http://localhost:8080/updateCenter/ and look at the status of plugins (may need to install another plugin)
          However you can see that

          * OWASP Markup Formatter Plugin antisamy-markup-formatter plugin is already installed. Jenkins needs to be restarted for the update to take effect
          * Pipeline workflow-aggregator plugin is already installed. Jenkins needs to be restarted for the update to take effect

          Both of these are incorrect.

          The wizard has requested the same version be installed multiple times.
          You can see this if you go to /pluginManager/installed and version 1.3 is installed - yet you can download to 1.3....

          So
          1) Jenkins should restart if it has installed plugins that require a restart to activate
          2) Jenkins should not try to install the same version of the plugin twice (infact it should not try to install any version of the same plugin twice - do it once and install the latest).

          For slow internet links the multiple isntalls will cause a longer than required setup time.

          This seems like it's an existing behavior in the plugin manager (would happen even if you installed these manually via the plugin manager). This should be fixed in the context of the plugin manager core, it's not about the setup wizard.

          Spike Washburn added a comment - This seems like it's an existing behavior in the plugin manager (would happen even if you installed these manually via the plugin manager). This should be fixed in the context of the plugin manager core, it's not about the setup wizard.
          Spike Washburn made changes -
          Labels Original: 2.0 2.0-beta community-bee New: 2.0 2.0-beta
          James Nord made changes -
          Attachment New: screenshot-1.png [ 32384 ]

          James Nord added a comment - - edited

          Still an issue with beta-2

          If I skip the plugin wizard and go to the plugin manager and choose the same set of 19 plugins and choose install, then some are also requested to be installed twice and Jenkins requires a restart. So not a new defect - but I guess a side effect of removing all those bundled plugins and everything depends on them!

          James Nord added a comment - - edited Still an issue with beta-2 If I skip the plugin wizard and go to the plugin manager and choose the same set of 19 plugins and choose install, then some are also requested to be installed twice and Jenkins requires a restart. So not a new defect - but I guess a side effect of removing all those bundled plugins and everything depends on them!

            kzantow Keith Zantow
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: