Community
Participate
Working Groups
We restart our Hudson instance weekly. Today we had 2 different Hudson instances(Sandbox and LTS) fall over. On restart all that is shown is the 'initial' Hudson install page, but you can't 'continue' past it as long as security is enabled, and disabling it requires hand editing hudson-security.xml. Once that's done, if you restart Hudson you are shown a 'plugin update' page, and only after you click the install->finish will the Hudson instance load the 'main' page. It seems that something in the 'check for updates' functionality is causing this state to occur. If we'd updated the core Hudson code it may be a little more understandable(but it still shouldn't require turning security off to get past), but for a plugin(Accurev) to do this seems excessive(especially as it hadn't been previously installed and things were fine) -M.
Relates to Bug: 395616 I think there are 2 issues here. 1. From what I understand Hudson detected that there were available "Mandatory" updates. Specifically a new plugin "AccuRev" was now mandatory and when Hudson was restarted, it decided that this plugin must be installed immediately before allowing us to continue to use Hudson. I don't believe this is good behaviour. While I could understand if Hudson core was updated by and administrator and now there are new plugins that need to be installed for it to be used this would be fine. But in this case all that happened was we restarted the Hudson service. 2. If your using security with Hudson. The "Initial Setup" page requires you to login as an admin user. However when I tried I was an admin user from LDAP and I was not able to get past this page using my credentials. I'm not sure what it's checking against but I guess the LDAP settings configured in Hudson was not enough. A workaround is to disable security temporarily to continue and install the Mandatory plugin then re-enable security once that's dealt with.
