SVN branches are not visible

Question

I have just installed Fisheye+Crucible (as docker container "atlassian/crucible") for evaluation. We are evaluating this as start with one product which has code on two SVN repositories.

Both SVN repositories have "trunk" branch and many other branches, as development is being done in branches. On repository configuration, SVN URL is entered exactly as what "svn info" command gives as repository root.

The problem is, that older SVN branches (those which had activity before installing Fisheye+Crucible) are not visible on Repositories->[repo name]->Activity->Branches.

How those older SVN branches can be scanned into system?

Alex John · Answer

Had the same thing happen. Fisheye only indexes from the moment you add the repo, so older branches stay hidden until you force a full rescan. In the repo settings try triggering a complete re-index or delete and re-add the repository that usually pulls the older branches in.

Dom Dain · Answer

You may need to trigger a full rescan of the SVN repository so Fisheye can pick up the older branch history. I’d also check the repository’s branch detection settings, since older inactive branches may not be discovered automatically.

Paul Collins · Answer

I suspect the problem is not the age of your svn branches but the overall structure of your repo. FishEye has "SVN Symbolic Rules" under "SCM Details" settings that control where it looks for trunk and branches.

The default structure used by FishEye is one where there's a directory containing just three directories: "trunk", "tags", and "branches'.  Each non-trunk branch is a subdirectory of the "branches" directory. If your repo has all the branch directories as siblings to your trunk, the default rules won't work. The good news is that "Symbolic" means there's a way to configure FishEye to understand a lot of different repo structures.

It's important that you *don't* tell FishEye that the parent to all the branches is "trunk". See the warning here: https://confluence.atlassian.com/fisheye/subversion-960155467.html

Then look here for the description of how to set up your SVN Symbolic Rules.

https://confluence.atlassian.com/fisheye/svn-tag-and-branch-structure-960155478.html

There is a date cutoff option somewhere. That might be useful just to do a shallow test setup to make sure your symbolic structure works. I think to get my large repo in I had to adjust Java memory settings to keep it from running out.

I think I did this once 10 years ago and don't remember how it works myself. But it worked. Good luck!