FishEye 2.2 : ClearCase
This page last changed on Jan 22, 2010 by edawson.
This page contains instructions for how to set up a ClearCase repository in FishEye, a configuration reference and a list of known issues.
On this page: RequirementsThe instructions on this page require the following applications:
Setting up a ClearCase RepositoryWhen adding or managing a ClearCase repository, carry out the following steps: ClearCase Repository Details
Inclusion/Exclusion SettingsThe following points provide guidelines for the settings which may need to be applied in order to restrict the number of ClearCase Projects/VOBs indexed by FishEye.
View CreationAs part of the repository scanning logic, FishEye will create a view for each Project (for ClearCase UCM environments) or VOB (for Base ClearCase) using the locations defined in the 'View Location' and 'View Storage Location' fields. This is required in order for the underlying 'cleartool' commands to be executed in the correct context. Please note that FishEye will not perform updates on these views - it is intended that these views will remain unpopulated. Indexing LogicIt may be helpful to understand how FishEye's ClearCase support carries out indexing. UCM ClearCaseThe ClearCase support will attempt to index all the available content within a ClearCase environment. The logic works as follows (ClearCase specific terms are underlined see definitions):
Base ClearCaseThe logic for the Base ClearCase support is similar to the UCM ClearCase support,
Allocating Time for Repository ScanningThe initial scan of a repository is a time and resource intensive operation, more so if the ClearCase repository being indexed is large (both in terms of the number of ClearCase projects and the number of change sets included in each project). In the Atlassian test environment (running in a virtual machine), each commit included in a change set would take approximately one second to complete (the time taken in a non-VM environment seems to be slightly faster at approx 700ms). You can use these numbers to estimate the time it will take to scan your repository; it could take many hours or possible days to complete. Changes included in 2.1.3Config.xml schema changesThe structure of the underlying schema for the ClearCase configuration config.xml file has changed. The effect of this is that for repositories created prior to version 2.1.3, the VOB/UCM Project Inclusion rules won't appear in the Administration UI. However, the previously entered values for these fields will still be used as part of the repository scanning logic. In order for these fields to be displayed in the Administration UI, the values for these fields should be re-entered. Interactive invocation of cleartool commandsAs a performance improvement measure, a number of the cleartool commands executed by FishEye as part of the repository scanning logic are now executed in 'interactive' mode. That is, a cleartool process (one per repository) is kept open for the duration of the indexing process. The execution of commands in interactive mode can be disabled by adding a 'disableInteractiveProcess' attribute to the specific ClearCase repository defined in the config.xml file. Performance ImprovementsSubsequent indexing operations for Base ClearCase repositories will take the last indexed date into account, so the 'cleartool lshistory' output will only include those changes that have not already been indexed. Changes included in 2.1.2In the first release, the include/exclude rules for VOBs and Projects were handled by the 'Include/Exclude' rules item on the administration page. Based on feedback received during initial version testing, this has been updated to provide additional flexibility:
Known IssuesThere are a number of known issues with ClearCase support in FishEye. These are listed below.
Further to this, by default ClearCase treats any files not defined in the 'default.magic' file as 'compressed' (for instance, property files are not included in the default.magic file). Only text-based type managers can be annotated (and hence, can be displayed via the 'Annotated Source' link). The type manager can be updated by performing the following steps: 1. Update the default.magic file to include appropriate rules that specify the type manager to use for files of a given naming convention (this will take effect for newly created elements) Further information on the ClearCase type manager is available on the following pages: Type Manager white paper
Feedback and SupportPlease raise a support ticket to seek assistance with FishEye ClearCase support. |
![]() |
Document generated by Confluence on Feb 18, 2010 23:51 |