-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Linux buildmaster 2.6.26-2-amd64 #1 SMP Tue Jan 25 05:59:43 UTC 2011 x86_64 GNU/Linux
Attempting to upgrade from 1.409.1 to 1.409.2 failed: Jenkins reported that an update was available but due to a server-side issue, it was then unable to actually download the new .war file.
Since then, Jenkins only displays:
Upgrade to Jenkins 1.409.2 is in progress or failed.
with no way to re-try the upgrade process (now that the issue on the server has been resolved). Also see attached screenshots.
Adding a simple "retry" button would help here.
For more context, see http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/5fdd91ec3c4080d0
- links to
[JENKINS-11016] Add an option to try again after a failed Jenkins upgrade
Assignee | New: Daniel Beck [ danielbeck ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR 1953 (Web Link)" [ 13594 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
It's not that difficult to download the jar manually and place it on the server. If it failed in the first place, it's not necessarily a bad idea to force the admin to log in, resolve the issue, and clean up.