Title: Message Title
Darrel Vuncannon commented on JENKINS-9802
Re: Manage Plugins section should be more informative and User freindly
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
Add Comment
