Command-line options
run
The run command starts Fisheye. This command runs Fisheye in the foreground. It does not fork a background process.
start
The start command has the same options as run, but starts Fisheye in the background.
Windows: Fisheye will be run in a separate cmd.exe window.
Unix: Fisheye will be run with nohup and the console output will be redirected to $FISHEYE_INST/var/log/fisheye.out.
Options (for both run and start):
| Load configuration from the file at |
| Do not print anything to the console. |
| Print extra information to the debug log. |
--debug-perf | This option is redundant and is now a synonym for --debug. |
The following --X prefixed options are currently available, but are typically used only for specific workarounds and edge cases in support scenarios. They may be removed or changed in any future release:
| Specifies the number of spaces to use to represent a tab character. The default is 8. |
| When rendering the directory tree on some pages, Fisheye calculates if each directory subtree is empty. For massive repositories, this calculation can cause the page to take a long time to render. This option disables the calculation that determines emptiness. If you start Fisheye with this flag, then empty directories will no longer show up as grey (i.e. deleted) and the option to hide them will also disappear. |
| Disables the generation of a full-text index for file content. This prevents further indexing, but does not delete any existing full-text indexes. Fisheye will not warn you if you specify this option but still try to do a content search. This option is useful if you do not use content search and you are finding Fisheye is taking a long time to index your content. The option is ignored for Git and Mercurial repositories. |
--Xno-slurp | Disables regular polling for indexing. We recommend that you disable polling for specific repositories in their configuration options, instead. |
--Xenable-git-content-hash-resolving-heuristic | This was used to speed up indexing by avoiding an exhaustive lookup of file revisions that give a particular content hash in Git repos. Git manifest support in Fisheye removed the need to use this option. It does still apply if a manifest upgrade has not completed. |
--Xdisable-head-detection | Disables branch head detection in DVCS systems (Git and Mercurial). |
--Xdisable-tags | Disables tag processing in DVCS systems. |
--Xlenient-patches | Fisheye will attempt to process non-standard patches. |
stop
The stop command stops a running Fisheye instance.
Options:
| Load configuration from the file at |
fullscan
Usage:
fisheyectl fullscan [options] [repname ...]
The fullscan command requests a full scan of the given repositories, or all repositories if no repository name is given.
Note: The fullscan command is only supported for CVS repositories.
Options:
| Load configuration from the file at |
rescan
Usage:
fisheyectl rescan [options] repname start end
Requests a rescan of the given repository between two specified revision ids.
Note: this operation is not supported by CVS repositories.
Options:
| Load configuration from the file at |
reindex
Usage:
fisheyectl reindex [options] [repname ...]
Requests a full reindex of the given repositories, or all repositories if no repository name is given.
Options:
| Load configuration from the file at |
scannow
The scannow command requests an incremental scan from the command line.
Usage:
fisheyectl scannow -s [repname ...]
Options:
| Run synchronously; i.e. the command will not terminate until the requested indexing operation is complete. |
- You can set the poll period to 'Never' in which case the repo will be viewable from the web UI but the repository will not be polled.
Repositories may be polled in the demand using this code:
fisheyectl.sh scannow [repname ...]
This will perform a one-time indexing operation.
Note: scannow can also be used on a repository which has a poll period.
backup / restore
Fisheye data can be backed up from the admin interface or command line. This page contains the command syntax, options and the required procedure to back up and restore your Fisheye instance: Backing up and restoring Fisheye data
svnrules
The svnrules tool ships with Fisheye 3.0, and later versions. It parses the SVN log and compares that against the SVN symbolic rules configured in Fisheye to find commits that are likely to be branch or tag creation changes for which there are no SVN symbolic rule defined. Find the details here: Verifying SVN symbolic rules