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

Manage Plugins section should be more informative and User friendly

    XMLWordPrintable

Details

    Description

      Manage Plugin Section Should be made more Information Friendly
      1) New Plugin should be marked as New!
      2) Updates Should be marked as Update!
      3) Outdated/Deprecated Plugin should be marked as Deprecated!
      4) Plugins should be sortable based on category, products (like maven. SVN etc.), stability

      Attachments

        Issue Links

          Activity

            Please This is new feature request

            jeebitesh Jeebitesh Kalantri added a comment - Please This is new feature request

            It would be very handy if we can see if a plugin is deprecated (like "M2 Extra Steps Plugin")!

            kreyssel Conny Kreyßel added a comment - It would be very handy if we can see if a plugin is deprecated (like "M2 Extra Steps Plugin")!

            It would be interesting to be able to filter (or have separate views, or different decoration in the plugin list) for plugins coming from different repositories.
            We want to make sure our developers can easily recognise whether they are installing a corporate plugin or a public one.

            rafaelrezend Rafael Rezende added a comment - It would be interesting to be able to filter (or have separate views, or different decoration in the plugin list) for plugins coming from different repositories. We want to make sure our developers can easily recognise whether they are installing a corporate plugin or a public one.

            I'm commenting based CloudBees' Jenkins November 2015 Newsletter soliciting input for Jenkins 2.0

            My Use Case: I NEVER want to upgrade a plugin to the latest version!

            My request to you is:

            • Make sure I can easily browse and install specific versions of plugins.
            • Also, help me verify their dependencies without automagically installing the dependency.
            Background

            I value stability in my Jenkins. A few times a year, I review the possible updates to our 100+ installed plugins by reading their change-logs and dependencies. I have confidence in the core LTS versions, but practically no plugin has earned my confidence with its latest version. Therefore, I often skip the latest version to avoid risk when my potential benefit is low. I prefer stability for my hundreds of developers.

            Timing is the other reason I need this feature. After I select my candidate plugin-versions, I test and soak them on a special Jenkins instance at my company, which takes a couple of weeks. When I'm ready to install them on my production instances, I only want the versions I tested. It's possible there's been new versions released since I started testing, but I don't want them.

            Lastly, it's difficult to manually check the dependencies for a latest plugin version, and it's worse/impossible for a previous version. I use the plugin manager's "Advanced" tab to load the specific version I want, but I understand that this skips automatic dependency checking. We Jenkins users that value stability need dependency checking on old versions too – but don't load a depended upon plugin-version without user confirmation, because I may not have tested it yet.

            Thanks in advance for your consideration,
            Darrel Vuncannon
            SW Configuration Management and Build Tools Team
            Garmin International

            darrelvun Darrel Vuncannon added a comment - I'm commenting based CloudBees' Jenkins November 2015 Newsletter soliciting input for Jenkins 2.0 My Use Case: I NEVER want to upgrade a plugin to the latest version! My request to you is: Make sure I can easily browse and install specific versions of plugins. Also, help me verify their dependencies without automagically installing the dependency. Background I value stability in my Jenkins. A few times a year, I review the possible updates to our 100+ installed plugins by reading their change-logs and dependencies. I have confidence in the core LTS versions, but practically no plugin has earned my confidence with its latest version. Therefore, I often skip the latest version to avoid risk when my potential benefit is low. I prefer stability for my hundreds of developers. Timing is the other reason I need this feature. After I select my candidate plugin-versions, I test and soak them on a special Jenkins instance at my company, which takes a couple of weeks. When I'm ready to install them on my production instances, I only want the versions I tested. It's possible there's been new versions released since I started testing, but I don't want them. Lastly, it's difficult to manually check the dependencies for a latest plugin version, and it's worse/impossible for a previous version. I use the plugin manager's "Advanced" tab to load the specific version I want, but I understand that this skips automatic dependency checking. We Jenkins users that value stability need dependency checking on old versions too – but don't load a depended upon plugin-version without user confirmation, because I may not have tested it yet. Thanks in advance for your consideration, Darrel Vuncannon SW Configuration Management and Build Tools Team Garmin International
            timja Tim Jacomb added a comment -

            All features in the description are now in the plugin manager

            timja Tim Jacomb added a comment - All features in the description are now in the plugin manager

            People

              kktest8 Kohsuke Kawaguchi
              jeebitesh Jeebitesh Kalantri
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: