A background thread was added that periodically checks an atlassian server to see if there are FishEye/Crucible updates available. The polling behaviour can be manipulated in the Server Settings page in the admin section. The polling URL and the interval can be manipulated.

On page Server Settings (http://edgy:6060/foo/admin/viewServerSettings.do):

• The "Update Notifications" widget says whether polling is currently enabled or disabled.
• If disabled, this will allow the user to enable polling by clicking "enable".
• Going from disabled to enabled always loads the default settings for url (http://update.atlassian.com) and interval (1 day).
• When enabled, the "Edit config" link appears to change the properties.
• Clicking "disable" removes the URL and interval values. Clicking "enable" again, loads up the defaults.

On page: Edit config (http://edgy:6060/foo/admin/editUpdatePolling-default.do)

• URL and interval are required parameters.
• It probably makes no sense for users to manipulate the polling URL (maybe it shouldn't even be there!)
• Negative intervals and zero are illegal.

General:

• The settings are saved to the config.xml using the newly introduced <checkForUpdates url="http://some/url" interval="2 days"/> tag located at the end of the <config/> tag.
• When the element is omitted, polling is disabled.
• When the url attribute is omitted, but <checkForUpdates/> is present, "http://update.atlassian.com" is used.
• When the interval attribute is omitted, but <checkForUpdates/> is present, "1 day" is used.
• To prevent a polling frenzy, intervals lower than 1 minute are always interpreted as 1 minute.