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
Community Members
Community Events
Community Groups

SVN custom folder structure

We're evaluating FishEye, to be used with our SVN (VisualSVN) repositories. Hence, we're looking at the built-in symbolic rules vs custom.

Existing SVN organisation is a bit ugly with projects and trunks scattered at different levels in repository, e.g.


Am I right in that this is really not recommended?

We do plan to migrate all code to a new SVN server so, should we aim to strictly standardise on the /project/trunk/... approach?

3 answers

1 accepted

0 votes
Answer accepted

If you have a single repository with mixed structure then you might need to create pseudo repositories in Fisheye to deal with the differences.

Your structure seems to represent the change in thought on how to organize svn repositories. Initially it was recommended that trunk/branches/tags was at the highest level of the repository. Later it was recommended that each project have their own trunk/branches/tags to make moving projects easier and being able to provide access to svn projects in an easier fashion.

The structure has evolved over a long period of time, and it's been a bit of a free for all. We are now going to implement a standard, which will help FishEye

I am sure there are other items, but the one pitfall I ran into was svn properties when reorganizing repositories. In particular svn:externals, where I needed to fix up the references.

For the projects that are dead, we just moved them to a separate area (we called it archive) with still active libraries getting a branch for archived project.

Questions answered. Thankyou

As long as there is structure in each repository, you can define it in FishEye and have it indexed.
If the structure differs from repository to repository, you'll have to configure the tag and branch structure regexps in FishEye correctly, which can be a lot of work.

If you have the opportunity to correct the structure of your SVN repos, that might be best.
See for the commonly used structures. You don't have to stick to those, you can use your own variation, as long as you use it consistently.

Thankyou for responding to this. We will take the opportunity to 'orgnise SVN properly' next time. Thanks

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

297 views 0 9
Join discussion

Community Events

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

Events near you