All Versions
Fisheye 4.2 DocumentationFisheye 4.1 Documentation
Fisheye 4.0 Documentation
More...
The 'Updater' repository option allows an administrator to manually trigger the actions described below, depending upon your repository type.
Poll Period |
How often FishEye will check to see if there have been any new commits into the SVN or Perforce repository. The default is 60 seconds. It is possible to set the period by units. For example: 10second, 1week. Valid units are 'second', 'minute', 'hour', 'day', 'week', 'month', 'year'. The default unit is days if only a number is added. |
FishEye will monitor your CVS history file CVSROOT/history
to determine what has changed in your repository. FishEye will also periodically scan the whole repository.
CVS is not always configured to create a history file. Talk to your CVS administrator.
The default values should be fine for most repositories. Leave a value blank to use the default value.
Value |
Description |
History file |
The location of the CVS history file. If relative, then it is relative to the CVS directory specified for this repository. Defaults to |
Full scan period |
How often FishEye will do a full scan of the repository. Defaults to 15 minutes. Specify an interval, such as '15 min', '2 hours', etc. A value of '0' disables the periodic full scan. (You can still use |
Strip prefix |
Prefix to strip off files found in the history file, to make them relative to this repository's CVS directory. |
Once you have changed the value, you will need to restart fisheye. The period begins from when the initial index completes, i.e. when you restart, your repos will be scanned in order (depending on the number of threads you have configured) and when this scan completes this is the start of the period.
For example, if you set one hour, then your next scan will begin one hour after your initial scan is complete.
Setting the full scan period to 0 can still trigger a full scan of CVS repositories in certain instances. Please refer to FE-2411 for more details. This is scheduled to be fixed in 2.1.x