I have an SVN repo that does not follow traditional conventions for organization. That is to say, I have a repo with lots of directories/sub-directories with various text and binary files. This is mostly used for storing and maintaing various scrtipts and configuration files. How can I configure teh FE repo settings to show all the directories/sub-directories (along with their commit history) if the structure does not meet conventions (ie: trunk, branches, tags)? When I try and browse the repo, nothing is displayed.
I know you have solved your query, but you might still need to do more to get the most out of Fisheye.
If you have a non standard directory structure for your Branches and Tags but want Fisheye to understand it, i.e. so it recognises what is a branch and what is tag, as opposed to a standard directory, you need to tell it what your structure is by means of regexes:
see the docs for details:
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot