Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,447
Community Members
 
Community Events
176
Community Groups

Display data for unconventional repository

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.

2 answers

1 accepted

0 votes
Answer accepted

I guess I had the configuation all wrong. I was putting the URL in SVN URL and the path in Path. Makes sense, but FishEye was expecting the trunk, tag, branch folders after the Path. I put the full URL in SVN URL (svn://fqdn/path) and all is well now. :)

0 votes

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:

http://confluence.atlassian.com/display/FISHEYE/SVN+Tag+and+Branch+Structure

Thanks Martin. For my case, there are no branches or tags as the repo is not used for writing code in the traditional sense.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events