Discussions > CollabNet TeamForge > How to use existing repository for project

forums
Discussion topic

Hide all messages in topic

All messages in topic

RE: How to use existing repository for project RE: How to use existing repository for project

Author	jmmooney
Full name	Justin Mooney
Date	2012-04-12 05:30:12 PDT
Message	Mark and Ananda, Thanks for the helpful replies. I am going to create a separate repository for each project and dump my current folders for each project into its respective repository. There is just two programmers in my group so little changes like these should not hamper our work.

RE: How to use existing repository for project RE: How to use existing repository for project

Author	anandakumara
Full name	Anandakumar Arumugam
Date	2012-04-11 21:39:56 PDT
Message	+1 to Mark's suggestion Here my 2 cents, If the repo contains bunch of project content, then think of the below 1. Keep the repo/product-component/module closely related in the same repo and project to make ease of development and integration. Example: Banking \|_Retail \|_Debit Cards \|_Credit Cards \|_Personal Loans 2. Move the independent project content to different repo and project which will give more isolation and independence Regards Anand -----Original Message----- From: Mark Phippard [mailto:mphippard at collab dot net] Sent: Wednesday, April 11, 2012 10:20 PM To: sfee at forums dot open dot collab dot net Subject: Re: How to use existing repository for project On Apr 11, 2012, at 11:58 AM, Justin Mooney wrote: > I think I included too much information in one post. > > Backgroung Info > I have a current repository on my personal machine that's running under an independent Subversion installation. I've migrated this repository to my TeamForge machine. > > Problem > What I am looking to do is use my existing repository with a project in TeamForge. Would I be better off crating a new repository for each and every project? It is probably a good idea to have a separate repository for each project as that allows you to most easily govern who can access the repository for each project. Also, a user working on a project might naturally expect the source code to appear within that project. Mark ------------------------------------------------------ http://forums.open.collab.net/ds/viewMessage.do?dsForumId=736&dsMessageI d=452605 To cancel your subscription to this CollabNet TeamForge discussion, please e-mail sfee-unsubscribe@forums.open.collab.net.

Re: How to use existing repository for project Re: How to use existing repository for project

Author	markphip
Full name	Mark Phippard
Date	2012-04-11 09:49:39 PDT
Message	On Apr 11, 2012, at 11:58 AM, Justin Mooney wrote: > I think I included too much information in one post. > > Backgroung Info > I have a current repository on my personal machine that's running under an independent Subversion installation. I've migrated this repository to my TeamForge machine. > > Problem > What I am looking to do is use my existing repository with a project in TeamForge. Would I be better off crating a new repository for each and every project? It is probably a good idea to have a separate repository for each project as that allows you to most easily govern who can access the repository for each project. Also, a user working on a project might naturally expect the source code to appear within that project. Mark

RE: Re: How to use existing repository for project RE: Re: How to use existing repository for project

Author	jmmooney
Full name	Justin Mooney
Date	2012-04-11 08:58:40 PDT
Message	I think I included too much information in one post. Backgroung Info I have a current repository on my personal machine that's running under an independent Subversion installation. I've migrated this repository to my TeamForge machine. Problem What I am looking to do is use my existing repository with a project in TeamForge. Would I be better off crating a new repository for each and every project?

Re: How to use existing repository for project Re: How to use existing repository for project

Author	markphip
Full name	Mark Phippard
Date	2012-04-11 08:33:47 PDT
Message	On Apr 11, 2012, at 11:10 AM, Justin Mooney wrote: > Hi. I just did a fresh install of Teamforge for Windows Server 2008 R2 64-bit. I have an existing subversion repository that was backed up and copied to c:/csvn/data/repositories. Teamforge sees it because I cannot create another repository of the same name. The problem I am having is that I cannot figure out how to use this existing repository in a new project, as well as browse any repository other than ones created for a project. Subversion Edge is being managed by TeamForge. You need to let TeamForge create the repository, and you can then load a dump file of your repository into the repository that TeamForge created. You could just replace the repository but if you do, you must make sure you copy the hooks that TeamForge added to the repository. > I want to be able to add the repository folder to a project if this is possible at all. > > My repository structure is: > -Project0 > -branches > -tags > -trunk > -Project1 > -branches > -tags > -trunk > -Project2 > -etc... Unless I completely misunderstood the first part, the content of your repository should not be relevant. Mark

How to use existing repository for project How to use existing repository for project

Author	jmmooney
Full name	Justin Mooney
Date	2012-04-11 08:10:35 PDT
Message	Hi. I just did a fresh install of Teamforge for Windows Server 2008 R2 64-bit. I have an existing subversion repository that was backed up and copied to c:/csvn/data/repositories. Teamforge sees it because I cannot create another repository of the same name. The problem I am having is that I cannot figure out how to use this existing repository in a new project, as well as browse any repository other than ones created for a project. Subversion Edge is being managed by TeamForge. I want to be able to add the repository folder to a project if this is possible at all. My repository structure is: -Project0 -branches -tags -trunk -Project1 -branches -tags -trunk -Project2 -etc...

Messages per page: