Medium Description
There is a bug in the FishEye indexing code for ClearCase repositories for branches that have been defined in a VOB, but have never been used. In the case of a customer (FSH-4960), there is a branch 'branchA' which has been defined in vob \vobB, but there no versions exist on the branch.
In detail:
- FishEye executes cleartool lstype -fmt %n\n -kind brtype -invob vob:\vobB to get list of branches for the VOB.
- One of the branches that is defined in the \vobB vob is branchA.
- FishEye retrieves the history for branch branchA by executing cleartool lshistory -fmt %Nd###%o###%u###'%c'###%Xn\n-nco -all -since 10-January-2007.10:08:12 -branch branchA \vobB. Cleartool returns 'Error: Branch type not found: "branchA".
- FishEye correctly intercepts the error and ignores the error and returns that there is no information for that branch in the VOB.
- FishEye incorrectly concludes that the VOB path was wrong and tries again with the leading slash.
- Cleartool returns an error which isn't caught and indexing stops.
The fix is to not retry with a leading slash. The problem could not be reproduced using a Linux installation where the vobs are mounted on \. It's likely (but not verified) that this problem only occurs on Windows using snapshot views.
A workaround is to explicitly exclude the branch(es) that are causing the problems in the FishEye repository configuration.
