1. Configure a subversion repository for a repository that includes the standard structure:
2. Disable built-in symbolic rules and use custom symbolic rules that include:
3. Test the rule with the structure above:
test path: tags/project-v1.0/common
Logical Path: common
Logical Tail: common
5. Build index
6. Browse repository in fisheye
EXPECT: Top level directories are:
The example is just for tags but trunk and branches are similarly affected.
Your symbolic rules look fine to me, but I think there is a bit of confusion over what FishEye shows. When you browse a Subversion repository, FishEye shows the physical paths. Your symbolic rules are used to determine branch/tag memberships and logical paths. You can verify this by going to the revision list for a file and checking the path, branch and tag information associated with each of the revisions.
While it was not what I expected to see, I do now find that it behaves as I expected. I can select trunk, drill down into trunk/common/Shared/.classpath, and switch to tag project-v1.0 to end up in tags/project-v1.0/common/Shared/.classpath, which is what I was after.
Thanks for providing me the confidence in my configuration to forge ahead :)
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events