Blames are the annotations available when viewing source files or diffs (in both Fisheye and Crucible) that allow you to determine who last modified a line of code and in which revision:
Fisheye and Crucible calculate blames from the internal repository cache during indexing time. On rare occasions that may not be possible. In such cases Fisheye and Crucible have a mechanism to retrieve blame data directly from the repository, either during indexing time, or when requested by browsing source files and diffs. However, as contacting the repository can be an expensive operation and may noticeably affect indexing time and/or responsiveness, this mechanism is off by default for both cases since 3.10.
Here are the system properties controlling blame calculations; the default values should be appropriate for most cases:
|システム プロパティ||説明||Available since||既定値|
Controls whether blames are calculated during indexing.
Note that blame calculation during indexing is disabled if the Store Diff Info setting is disabled. See Store diff info.
Controls whether blame data is retrieved from the SCM during indexing (when blame couldn't be based on ancestors).
Controls whether for all missing blames (when blame couldn't be calculated or retrieved during indexing) Fisheye and Crucible will retrieve blames from the repository. This happens during the web request - when users request blame data when viewing the file or diff.
When blame data is not available, the Author and Revision columns display "n/a" like this:
Blames may be not available:
- When indexing of a particular revision has not yet completed. This is a temporary state and blames should appear when indexing has finished.
- When the blame calculation failed during indexing and the
fisheye.enable.request.blame.calculationis set to false (the default value).
- If the repository configuration property Store Diff Info setting is disabled. See Store diff info.
- In patch files uploaded to the review. See Creating patch files for pre-commit reviews.