School Assignment? Project Due Tomorrow? Chat LIVE With A Programming Expert!

Welcome to Dream.In.Code
Become an Expert!

Join 300,391 Programmers for FREE! Get instant access to thousands of experts, tutorials, code snippets, and more! There are 1,575 people online right now. Registration is fast and FREE... Join Now!




SVN Repositories vs. Folders

 

SVN Repositories vs. Folders

killnine

14 Jun, 2009 - 04:25 PM
Post #1

D.I.C Head
**

Joined: 12 Feb, 2007
Posts: 159



Thanked: 16 times
My Contributions
So I am in the process of creating a number of projects (a GUI program, a WCF service, etc.) and I want to be able to check them out of subversion individually.

However, I dont know if it is better to create separate repositories for each project or to create a single repository and just make folders within it.

I am trying to set up my development system with Atlassian's Fisheye (http://www.atlassian.com/software/fisheye/).

I am pretty new to SVN (other than using it to pull the latest software out for *nix distros) so any suggestions or insight would be greatly appreciated. Thanks guys.

User is offlineProfile CardPM
+Quote Post


Oler1s

RE: SVN Repositories Vs. Folders

14 Jun, 2009 - 06:55 PM
Post #2

D.I.C Addict
****

Joined: 4 Jun, 2009
Posts: 639



Thanked: 66 times
My Contributions
QUOTE
However, I dont know if it is better to create separate repositories for each project or to create a single repository and just make folders within it.
It's an organizational question up to you. When I used Subversion, I would group tightly coupled projects together. By that I mean those in charge of working one project are definitely going to want access to the development source of the other. For example, if my code used zlib, this would be an example of not having such coupling. I just want the library. I don't care about the actual repository. On the other hand, a repository where I had two projects, one for a library, and one for the GUI, made sense. If you're trying to extract some kind of rule on grouping projects, you shouldn't. Heck, for configuration purposes, you might as well dump all projects into one single repository. If it becomes unmanageable later on, just split up the projects.

The wildcard is Fisheye. I haven't used it, and I don't know what the configuration quirks are. From briefly looking at their online documentation, it looks like Fisheye has approached the issue (the relevant document page on repository layout)) in a rather sane and intuitive manner. So it looks like Fisheye won't interfere in your choices. One repository, multiple repositories: all up to you.
User is offlineProfile CardPM
+Quote Post

killnine

RE: SVN Repositories Vs. Folders

15 Jun, 2009 - 07:20 AM
Post #3

D.I.C Head
**

Joined: 12 Feb, 2007
Posts: 159



Thanked: 16 times
My Contributions
QUOTE(Oler1s @ 14 Jun, 2009 - 06:55 PM) *

QUOTE
However, I dont know if it is better to create separate repositories for each project or to create a single repository and just make folders within it.
It's an organizational question up to you. When I used Subversion, I would group tightly coupled projects together. By that I mean those in charge of working one project are definitely going to want access to the development source of the other. For example, if my code used zlib, this would be an example of not having such coupling. I just want the library. I don't care about the actual repository. On the other hand, a repository where I had two projects, one for a library, and one for the GUI, made sense. If you're trying to extract some kind of rule on grouping projects, you shouldn't. Heck, for configuration purposes, you might as well dump all projects into one single repository. If it becomes unmanageable later on, just split up the projects.

The wildcard is Fisheye. I haven't used it, and I don't know what the configuration quirks are. From briefly looking at their online documentation, it looks like Fisheye has approached the issue (the relevant document page on repository layout)) in a rather sane and intuitive manner. So it looks like Fisheye won't interfere in your choices. One repository, multiple repositories: all up to you.



Looking at the documentation, I think I will go with top-level project directories and have my trunk/branch/tags underneath. That way I can have a single repository for a project (SomeProjectGUI, SomeProjectService, SomeProjectDataAccess), but have the leeway to create a new repo for a very different project (WindowsManagerProjectGUI, WindowsManagerProjectService...etc).

Thanks for the insight, more comments are def. welcome!
User is offlineProfile CardPM
+Quote Post

Fast ReplyReply to this topicStart new topic

Time is now: 11/7/09 09:46PM

Live Help!

Be Social

Dream.In.Code RSS Feed Dream.In.Code LinkedIn Group Follow Us On Twitter Fan Us On Facebook

Tutorials

Programming

Web Development

Reference Sheets

Code Snippets

DIC Chatroom

Bye Bye Ads

Monthly Drawing

Thumb Drive

Top Contributors

Top 10 Kudos This Month