[JIRA] (JENKINS-59681) Version selection for Jenkins Automatic Upgrade feature

[simon.schwarz@arvato.com (JIRA)]

Simon Schwarz created an issue

Jenkins / JENKINS-59681 Version selection for Jenkins Automatic Upgrade feature Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-10-07 08:57 Environment: Jenkins 2.187 Labels: upgrade update Priority: Minor Reporter: Simon Schwarz When automatically upgrading to a newer version of Jenkins there is only one button which upgrades to the latest version. In the changelog there are sometimes issues listed with that latest version and people had to roll back. I would like to be able to select the version which Jenkins gets upgraded to. To achieve this, the upgrade process must be done manually right now.   Please implement a selection for the automatic upgrading process. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-59681

Re: Version selection for Jenkins Automatic Upgrade feature Would not hold my breath here as this requires a significant project infra extension for very little benefit (just hold off updating for a week, or go the manual way). Speaking as a co-maintainer of core and the update center, you can probably consider this "Won't Fix" unless you're interested in doing this yourself, or able to get someone else to take an interest here.

Add Comment

[simon.schwarz@arvato.com (JIRA)]

SSchwarz commented on JENKINS-59681

Re: Version selection for Jenkins Automatic Upgrade feature

Thank you Daniel for your answer! If it is a lot of work, I will go manual. My hope was that this is just a small UI change adding a dropdown and then downloading and installing another version.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-59681

Re: Version selection for Jenkins Automatic Upgrade feature

We only advertise a single (the newest) release per component in the metadata Jenkins downloads to implement Manage Plugins and the Core Update Monitor, and the JSON structure does not gracefully extend to further releases.

Add Comment