Derik Whittaker

Syndication

News


Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
Clean Slate - Creating a Good Hierarchy in a Source Repository
It is not everyday that you get the luxury of starting from scratch when setting up a Source Repository.  So when our team found out that with the installation of our new VSTS server we would also be able to create a new hierarchy for the repository we were excited.  Like most source repositories, a few years, and no policing of the repository has lead to one big ugle of a repository. 

When we started to plan how the new repository would be structured, we wanted to try to look to the future as well as plan for the other teams that would be migrating to VSTS over the coming months.  Our goal with the new structure is to set up a simple, yet effective hierarchy that can be easy to follow and easy to extend.

Here is the structure we have come up with so far

//ROOT
    /Shared
        -> Shared Project
        -> Shared Project's Test

    /Group A (this is a team withing the department)
        -> Project A
            -> Sub folder
        -> Project B
            -> Sub folder
        -> Shared Project (would be any common libraries shared at the team level)
        -> Sandbox

    /Group B

        -> Project A
            -> Sub folder
        -> Project B
            -> Sub folder
        -> Shared Project (would be any common libraries shared at the team level)
        -> Sandbox

    /Group A Branches
        -> Project A
        -> ...
        -> ...

The rational behind this structure is that we want each team/group to have their own space, but still have a location for any department wide assemblies to go.  We wanted to move all branches out of the dev directories in order to allow us to do a get from the root of a group/teams folder (i.e., do a get on //Root/Group A) and not worry about getting all our branches.

Let me know what everyone thinks.  Is there a better way, is this too complicated.

Thanks


Posted 03-09-2007 7:15 PM by Derik Whittaker
Filed under:

[Advertisement]

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Subscribe
Google Reader or Homepage

del.icio.us CodeBetter.com Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl CodeBetter.com Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of Devlicio.us
Red-Gate Tools For SQL and .NET

NDepend

SlickEdit
 
SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
LiteAccounting.Com
DevExpress
Fixx
NHibernate Profiler
Unfuddle
Balsamiq Mockups
Scrumy
JetBrains - ReSharper
Umbraco
NServiceBus
RavenDb
Web Sequence Diagrams
Ducksboard<-- NEW Friend!

 



Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers

 

Community Server (Commercial Edition)