[FishEye ナレッジ ベース]
This page lists the Java VM system properties which may be set to control certain aspects of FishEye and Crucible's behaviour. Please refer to Setting JVM System Properties for how to set these properties in your instance.
Note that system properties that only relate to Crucible have names beginning with crucible.
FishEye/Crucible must be restarted for changes to become effective.
このページの内容
General properties
| プロパティ | Legal values | 既定値 | 説明 | バージョン |
|---|---|---|---|---|
crucible.detect.metadata.revision.changes | true/false | true | If true, detects and disables creation of reviews from changesets which contain metadata only changes (e.g svn property changes). Read more here. | 2.6.0 以降 |
crucible.review.content.size.limit | number of file revisions allowed in a review | 800 | Limits the "size" of a review to prevent extremely large reviews accidentally being created and potentially slowing the instance down. | 2.10.0 以降 |
fisheye.blame.calc.enable | true/false | false | Controls whether the FishEye server will scan content files to determine the lines of code (LOC) count. | 3.4.0 以降 |
fisheye.branch.recently.active.check.limit
| number of branches | 250 | Used in CommitGraph to control sorting of branches. If more than the limit, sorted alphabetically, otherwise sorted by recent activity. | 2.6.0 以降 |
fisheye.changeset.paths.limit | number of paths | 10000 | This setting is to prevent extremely large changesets (which are often the result of an error) from slowing FishEye/Crucible down. See Indexed paths truncated at 10000 for the messages that are logged if the value is reached. | |
fisheye.git.http-backend-timeout
| Integer milliseconds | 3600000 | This property sets the amount of time that the FishEye server should allow the underlying Git process to execute when attempting to serve a Git push or pull request. | 2.7.3 以降 |
fisheye.p4.disable.ancestry | true/false | false | If true, stops FishEye from processing P4 ancestry information. Change lists will still be assigned to branches. If you do not use stable Perforce branchspecs to manage branches, set this to true. | 2.7.5 以降 |
fisheye.p4.disable.branchspecs | true/false | false | If true, stops FishEye from reading Perforce branch specs. All change lists will appear on the 'head' branch. If you do not use stable Perforce branchspecs to manage branches, set this to true. | 2.7.13 以降 |
fisheye.search.max.repositories | number of repositories | 100 | Used by FishEye to limit the search to the top n repositories (by alphabetical order) when a cross-repository search is performed. | 2.7.12 以降 |
jetty.http.headerbuffersize | bytes | 4096 | This controls the size of the largest HTTP header value that FishEye will allow (through its embedded servlet engine, Jetty). Some authentication systems require larger header values. | 1.6.5 以降 |
org.eclipse.jetty.server.Request.maxFormContentSize | bytes | 3000000 | Max form content size – increase this value if your Git push fails with HTTP error 411 (see this KB article: Git PUSH results in RPC failed, result=22, HTTP code = 413) | 3.0.0 以降 |
FishEye pipeline indexing
See Pipelined indexing.
| プロパティ | Legal values | 既定値 | 説明 | FishEye version |
|---|---|---|---|---|
fisheye.pipeline.batch.cslimit | 1 - 50000 | 10000 | The pipeline processes changesets in batches. A bigger batch size reduces the number of calls to the underlying SCM, but also increases heap consumption and reduces the concurrency of the pipeline. Smaller batch sizes increase the concurrency of the pipeline, reduce heap consumption, but result in more calls to the underlying SCM. | 3.0.0 以降 |
fisheye.pipeline.batch.pathlimit | 1000 - 120000 | 60000 | The pipeline processes changesets in batches. This property sets the maximum allowed number of unique paths in a batch (summed across changesets). A higher value will reduce the number of calls to the underlying SCM, at the expense of more heap consumption. | 3.0.0 以降 |
fisheye.pipeline.fairness | true, false | true | If If | 3.0.0 以降 |
fisheye.pipeline.threads | 4-1000 | The number of processor cores detected, or 4, whichever is greater | The number of threads available to work on indexing tasks. A higher value allows for potentially greater concurrency in indexing activities, but will increase the load on the server and the load on your SCM. | 3.0.0 以降 |
Git manifest
| プロパティ | Legal values | 既定値 | 説明 | バージョン |
|---|---|---|---|---|
fisheye.manifest.forceupgrade | true or false | true | Controls whether manifests are upgraded before repository indexing continues or as a background process as time permits during regular indexing | 3.4.0 以降 |
fisheye.manifest.maxdepth | 1-100 | 3 | Controls how many delta manifests are written in a chain before a full manifest is written | 3.4.0 以降 |
fisheye.manifest.maxupgradepaths | 100 upwards | 500000 | The maximum number of paths that will be upgraded before a batch is committed to the FishEye index | 3.4.0 以降 |
fisheye.manifest.upgradebatch | 10 upwards | 1000 | When performing background upgrading this is the minimum number of changesets that will be upgraded in each indexing poll period. | 3.4.0 以降 |
Mail client
You can tune the mail client in FishEye with system properties.
The available system properties are listed and described at https://javamail.java.net/nonav/docs/api/com/sun/mail/smtp/package-summary.html.
For example, mail.smtp.quitwait=false can be used in cases where the FishEye mail server doesn't respond to a QUIT message, and causes the mail client to hang.
概要
コンテンツ ツール
アプリ
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.