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.

projects/trunk/subproject/subproject/...
projects/subproject/subsubproject/trunk/...

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

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.

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 http://svnbook.red-bean.com/en/1.1/ch04s07.html#svn-ch-4-sect-7.1 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

Questions answered. Thankyou

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Marketplace Apps

Tips on how to choose the best estimation method for your planning

Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...

29 views 0 10
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you