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

It is unclear that the items with ** are dependencies during plugin install on 2.0

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • jenkins-2.0-alpha

      When the plugin installed wizard is installing plugins, it shows a plugin in black and then it can have other plugins with ** in front that are grey. It is unclear that these grey plugins are the dependencies. There is also a lot of wasted whitespace area during this time as well. The whole area to the left of the installing list is just blank. More information could be provided in that space during install. Perhaps some tips on using Jenkins.

          [JENKINS-33246] It is unclear that the items with ** are dependencies during plugin install on 2.0

          Alex Earl created issue -

          Daniel Beck added a comment -

          The absolute minimum here would be a tooltip on hover. It's not clear why dependencies, which are plugins after all, don't get a full "box" – would allow for a better progress indicator as well.

          Daniel Beck added a comment - The absolute minimum here would be a tooltip on hover. It's not clear why dependencies, which are plugins after all, don't get a full "box" – would allow for a better progress indicator as well.
          Daniel Beck made changes -
          Labels Original: 2.0 New: 2.0 2.0-feedback
          Daniel Beck made changes -
          Labels Original: 2.0 2.0-feedback New: 2.0

          Patrick Wolf added a comment -

          I might be biased because of this ticket and seeing it before but I thought you could tell they were dependencies. Would that list overwhelm new users, danielbeck? That would create quite a few boxes.

          Although, the Mailer Plugin does have it's own box and when you view it on the Plugin Manager page it is shown as a dependency of several other plugins. This seems inconsistent.

          Patrick Wolf added a comment - I might be biased because of this ticket and seeing it before but I thought you could tell they were dependencies. Would that list overwhelm new users, danielbeck ? That would create quite a few boxes. Although, the Mailer Plugin does have it's own box and when you view it on the Plugin Manager page it is shown as a dependency of several other plugins. This seems inconsistent.

          Daniel Beck added a comment -

          Well, they do get installed, and even shown on the side panel. If it were explicit about "Installing Foo plugin which is a dependency of Bar plugin, Baz plugin" that should be fine I think. We're showing dependencies on the selection list anyway.

          Although, the Mailer Plugin does have it's own box and when you view it on the Plugin Manager page it is shown as a dependency of several other plugins. This seems inconsistent.

          Not sure what you mean. A plugin can be both available for selection on the list at the beginning, and also be a dependency. What the list currently does not do is indicate which plugins in the list already get automatically installed because they're dependencies of another plugin that is checked – another minor RFE?

          Daniel Beck added a comment - Well, they do get installed, and even shown on the side panel. If it were explicit about "Installing Foo plugin which is a dependency of Bar plugin, Baz plugin" that should be fine I think. We're showing dependencies on the selection list anyway. Although, the Mailer Plugin does have it's own box and when you view it on the Plugin Manager page it is shown as a dependency of several other plugins. This seems inconsistent. Not sure what you mean. A plugin can be both available for selection on the list at the beginning, and also be a dependency. What the list currently does not do is indicate which plugins in the list already get automatically installed because they're dependencies of another plugin that is checked – another minor RFE?

          Ulli Hafner added a comment -

          I would rather not show the dependencies in the new dialog: the dialog is especially for new users, they might get confused if there are now a lot of additional things that are going to be installed. (It's ok in the old dialog).

          I also would recommend to remove the dependencies tooltip in the selection dialog (or use an explicit action to show the dependencies).

          Ulli Hafner added a comment - I would rather not show the dependencies in the new dialog: the dialog is especially for new users, they might get confused if there are now a lot of additional things that are going to be installed. (It's ok in the old dialog). I also would recommend to remove the dependencies tooltip in the selection dialog (or use an explicit action to show the dependencies).

          Christopher Orr added a comment - - edited

          I agree — I certainly found the dependency tooltop to be unnecessary.

          Christopher Orr added a comment - - edited I agree — I certainly found the dependency tooltop to be unnecessary.

          Daniel Beck added a comment -

          FWIW dependency presentation is going to be changed a bit in a PR (https://github.com/jenkinsci/jenkins/pull/2009).

          Daniel Beck added a comment - FWIW dependency presentation is going to be changed a bit in a PR ( https://github.com/jenkinsci/jenkins/pull/2009 ).

          Daniel Beck added a comment -

          Also, enjoy all the additional dependencies from JENKINS-33296. May be bad enough that we need to require fairly recent core dependencies for plugins in this dialog, otherwise they'd have giant dependency lists.

          Daniel Beck added a comment - Also, enjoy all the additional dependencies from JENKINS-33296 . May be bad enough that we need to require fairly recent core dependencies for plugins in this dialog, otherwise they'd have giant dependency lists.

            kzantow Keith Zantow
            slide_o_mix Alex Earl
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: