|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Harald: For me, it was because I installed from RPM and decided I want Jenkins to be auto-upgradeable. So I ran chown jenkins /usr/lib/jenkins/jenkins.war. The button to Upgrade Automatically did appear, as did the exception after I clicked it. The jenkins user needs write access to the containing folder, as that is where the downloaded file is stored.
An alternative solution have been to download to a guaranteed writable file in the temp dir, but being able to rename the .war to .bak (backup file) before upgrading seems like a good idea as well, so now the button only shows up when the folder is writable as well.