[#FISH-154] Fisheye and Fisheye plugin should better handle rescans after update of non-versioned property

JIRA FishEye Plugin

Fisheye and Fisheye plugin should better handle rescans after update of non-versioned property

Created: 04/Apr/08 02:46 PM Updated: 11/Apr/08 01:34 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

1.5

Time Tracking:

Not Specified

Labels:

Description

« Hide

I have a user who occasionally updates here commit comment, then complains that she needs to do a 'rescan' in Fisheye, and a cache clear in Jira/Fisheye Plugin administration, in order for the corrected comment to be visible.

Ought to be easier

All

Comments

Work Log

Change History

FishEye

Crucible

Related Builds

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Tim Pettersen - 06/Apr/08 07:03 PM

Hi Peter,

There will be an explicit method for cache clearing in an upcoming release of the plugin (instead of the current workaround of updating the FishEye Configuration) but this will still require some action on the part of the user.

The caching of commit data in JIRA is designed to boost performance by preventing too many queries to FishEye. However, you could disable the cache altogether by setting the Revision Cache Size field on the JIRA FishEye plugin configuration page to 1 (0 will not work in the currently released version, see ~~FISH-120~~ for details).

cheers,
Tim

[ Permlink | « Hide ]

Tim Pettersen - 11/Apr/08 01:34 AM

As of the upcoming 1.5 release, there will be cache statistics and a cache flushing mechanism available via the UI.

To flush the cache, navigate to the FishEye Configuration page in the Administration section and look for the link Statistics link next to the Revision Cache Size parameter. This will take you to a cache statistics screen with a Flush Cache button. If you need to rescan the FishEye repository and you want JIRA to pick up the changes immediately, just press this button.