Details
-
Type:
Improvement
-
Status: Done (View Workflow)
-
Priority:
Minor
-
Resolution: Won't Do
-
Component/s: plugin-site
-
Labels:
-
Environment:plugins.jenkins.io web site
-
Similar Issues:
Description
There's no obvious way to download the current version of a plugin. I tried this on IE & Chrome.
I have to visit the archives and download from there. That makes for twice the clicking, which makes manually downloading plugin updates that much more painful for those of us without an Internet connection for our Jenkins servers.
Filed as a bug since the previous incarnation of the plugins site did have a direct link to the current version.
Attachments
Activity
I wrote a ruby script to manage the dependencies, so that I can get the order of the plugins right. I've since written a powershell script to download the latest version of each of the plugins, so I've worked around this issue.
My workflow for updating plugins is a bit convoluted, I have a Jenkins installation on my personal laptop, and use it to grab the desired plugins and updates. I then run the ruby script to list the plugins in order of dependency. I email that list to my work address. From my work laptop, I feed the list to the powershell script that grabs the packages from the Jenkins plugins site. I transfer the lot to the server, and load them manually from the plugins page. Woe is me if I try to dump all the packages directly in the plugins directory and restart.
I tried loading them via a Groovy script from the Jenkins console, but although dynamic loading appeared to work, items I loaded earlier weren't recognized even though I'd restart when I got an exception saying a restart was needed.
I'd be very happy to hear of a better way to update plugins (given the server doesn't have an Internet connection).
Why hide the most current version of the plugin? What's the now preferred way of getting a new plugin?
a ruby script to manage the dependencies, so that I can get the order of the plugins right
This looks so much like a unique approach that I doubt we want to add specific support for it. As I wrote, we need something better for offline installs, but that's probably not going to be a prominent download link.
Why hide the most current version of the plugin? What's the now preferred way of getting a new plugin?
The current version of a plugin is to the top left, beside the plugin title.
It would help if the version were a link, rather than just text.
I'm strongly against providing the majority of users with the tools to work around the Update Center and proper dependency management for their plugins.
If somebody wishes to grab the plugin versions directly, I am comfortable assuming they know how to parse the update-center-json for links.
While we need a solution for offline systems, I'm not sure more prominent download links are the solution, given the mess that's manual dependency management.